!zghijEASpYQWYFzriI:nixos.org

Hydra

342 Members
99 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
13 Nov 2024
@inayet:matrix.orgInayet joined the room.22:16:32
15 Nov 2024
@asymmetric:matrix.dapp.org.uk@asymmetric:matrix.dapp.org.uk left the room.11:46:10
@Ericson2314:matrix.orgJohn Ericson das_j: Mic92 should we decide for nix-eval-jobs? 16:24:18
@Ericson2314:matrix.orgJohn Ericson * das_j: Mic92 should we decide for nix-eval-jobs and Hydra? 16:24:24
@Ericson2314:matrix.orgJohn EricsonI was would like to see the code dedup done :)16:24:34
@Ericson2314:matrix.orgJohn Ericsonmeson one is passing now too, nicely16:24:46
@Ericson2314:matrix.orgJohn EricsonWith these changes, we can do one mega dev shell with nix perl bindings, nix-eval-jobs, and hydra, and change everything at once if we want :D16:25:39
@joerg:thalheim.ioMic92 John Ericson: you want one mega repo? 17:15:41
@Ericson2314:matrix.orgJohn Ericson Mic92: nope! 17:15:50
@Ericson2314:matrix.orgJohn Ericsonjust I unpack a bunch of repos locally17:15:58
@Ericson2314:matrix.orgJohn Ericsonand then make separate PRs17:16:07
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.de
In reply to @Ericson2314:matrix.org
das_j: Mic92 should we decide for nix-eval-jobs and Hydra?
I repeat my Github point which is that there is currently nobody willing and/or capable of maintaining that in-tree for hydra
17:48:36
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.deSo it can only go up from here17:48:42
@Ericson2314:matrix.orgJohn Ericson @janne.hess:helsinki-systems.de: maybe I saw those words twice but didn't understand them 19:42:15
@rick:matrix.ciphernetics.nl@rick:matrix.ciphernetics.nlThanks for fixing up CA derivations while you were at it πŸ™ŒπŸΌ, guess it was a useful test to add πŸ˜Άβ€πŸŒ«οΈ20:02:38
@Ericson2314:matrix.orgJohn Ericson Mindavi: oh you can be sure I won't cause a CA regression haha 20:03:56
@Ericson2314:matrix.orgJohn Ericson
In reply to @janne.hess:helsinki-systems.de
So it can only go up from here
are you saying it is worth merging? because no one wants to maintain hydra-eval-jobs?
20:04:55
@rick:matrix.ciphernetics.nl@rick:matrix.ciphernetics.nlI would think it's a good thing to use nix-eval-jobs in hydra instead of trying to maintain in the hydra repo20:07:26
@Ericson2314:matrix.orgJohn Ericson Mindavi: I think we all agree, I just don't wanna merge my own PR 20:08:58
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.de
In reply to @Ericson2314:matrix.org
@janne.hess:helsinki-systems.de: maybe I saw those words twice but didn't understand them
I'm sorry, not sure what was wrong with my grammar. The hydra component lacks maintainership which makes a switch to a maintained component a good idea. Is this grammar more understandable?
21:39:30
@Ericson2314:matrix.orgJohn Ericson das_j: gotcha, so you are saying this is definitely a net improvement, right? 21:40:06
@Ericson2314:matrix.orgJohn Ericsonif you like it, feel free to hit the merge button21:40:42
@Ericson2314:matrix.orgJohn EricsonI can inform the rest of the SC but I would not block a decision on this21:40:58
@janne.hess:helsinki-systems.de@janne.hess:helsinki-systems.de
In reply to @Ericson2314:matrix.org
das_j: gotcha, so you are saying this is definitely a net improvement, right?
Pretty much, apart from the fact that it's nix-community. Which is not something I have a personal issue with but I can imagine other people do
21:41:31
@Ericson2314:matrix.orgJohn EricsonI say better to ask for forgiveness than permission :)21:41:54

Show newer messages


Back to Room ListRoom Version: 6