!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

402 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.122 Servers

Load older messages


SenderMessageTime
25 Mar 2026
@hexa:lossy.networkhexaeh, of course you fixed it :D22:58:13
26 Mar 2026
@ss:someonex.netSomeoneSerge (matrix works sometimes)Has nobody ever needed to override hydra-dev's baseDir? Makes me feel I'm doing something wrong...03:37:40
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)Hm so somehow hydra wound up buillding the nix installer script incorrectly https://github.com/NixOS/nix/issues/15564#issuecomment-4132297971'07:34:34
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)Botched build input on remote builder? Any chance we can poke at the tarball store path at https://hydra.nixos.org/build/325163674#tabs-buildsteps (sleepy-brown) if it hasn't been GC'd yet?07:36:24
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)Thanks, no need. I figured it out - hydra got into a franken build situation09:21:25
@beat_link:matrix.orgBeatLink joined the room.12:01:29
@beat_link:matrix.orgBeatLinkHey, is it true that if i contribute to nixpkgs i can get an invite to the org?12:01:58
@hexa:lossy.networkhexa #org_owners:nixos.org if you didn't get one 12:03:38
@joerg:thalheim.ioMic92 @hexa:lossy.network: we should maybe make some time to test the new hydra stuff. I'll thinking also about some auto deploy for staging 21:46:36
@joerg:thalheim.ioMic92* @hexa:lossy.network: we should maybe make some time to test the new hydra stuff. I'll thinking also about some auto deploy for staging hydra21:47:02
@joerg:thalheim.ioMic92Told John to test staging a bit more21:51:29
@hexa:lossy.networkhexasure, why not23:35:47
@hexa:lossy.networkhexaapparently you wanted to deploy to prod on tuesday23:35:58
@hexa:lossy.networkhexaand today I got asked again when it will be deployed23:36:11
@hexa:lossy.networkhexaI will be away over the weekend mostly23:37:14
@hexa:lossy.networkhexabut let's schedule something for next week23:37:27
27 Mar 2026
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pull/46009710:44:10
@hexa:lossy.networkhexa @emilazy:matrix.org @k900:0upti.me @vcunat:matrix.org let's make a call on this 10:44:33
@vcunat:matrix.orgVladimír ČunátIt certainly looks good at a glance and in principle.10:47:34
@vcunat:matrix.orgVladimír ČunátBut I haven't thought about details, e.g. whether it's OK to have this nesting (aggregate of aggregates).10:48:40
@vcunat:matrix.orgVladimír ČunátOverall the situation around what's channel blockers and what isn't - I find it messy, not very maintained.10:49:44
@vcunat:matrix.orgVladimír ČunátI suppose we can merge optimistically.10:57:00
@k900:0upti.meK900I think it's fine unless there's a reason Hydra will explode11:02:37
@emilazy:matrix.orgemilyoh I had a suggestion around this in general11:02:38
@k900:0upti.meK900But it would be nice to maybe one day kill off the branch separation11:02:52
@emilazy:matrix.orgemilyfrom before this PR actually11:03:04
@emilazy:matrix.orgemilycan't we just merge the jobsets. like keep the channel advancement conditions decoupled but kill nixpkgs:unstable11:03:43
@emilazy:matrix.orgemilythat way you can much more easily pick commits that are both nixpkgs-unstable and nixos-unstable11:04:05
@k900:0upti.meK900Conceptually yes, but it would require significant channel-scriptage11:04:14
@emilazy:matrix.orgemilyand Hydra saves queueing and building a bunch of redundant Linux jobs from nearby commits11:04:22

Show newer messages


Back to Room ListRoom Version: 6