!UNVBThoJtlIiVwiDjU:nixos.org

Staging

391 Members
Staging merges | Running staging cycles: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Astaging-next+head%3Astaging-next-25.11 | Review Reports: https://malob.github.io/nix-review-tools-reports/128 Servers

Load older messages


SenderMessageTime
21 May 2026
@jkarlson:kapsi.fiEmil Thorsøejust did not realise, it was the patched version11:11:30
22 May 2026
@luckshiba:matrix.orgLuckShiba joined the room.19:03:02
@jonhermansen:matrix.orgJon Hermansen changed their display name from jonhermansen to Jon Hermansen.19:18:38
23 May 2026
@vcunat:matrix.orgVladimír ČunátI assume Hydra won't have much to do for the next 24h, i e. before the branch-off happens.04:37:30
@vcunat:matrix.orgVladimír Čunát* I assume Hydra won't have much to do for the next 24h, i.e.before the branch-off happens.04:37:46
@vcunat:matrix.orgVladimír Čunát* I assume Hydra won't have much to do for the next 24h, i.e. before the branch-off happens.04:37:59
@freshreplicant:matrix.orgfreshreplicant joined the room.15:19:46
24 May 2026
@hexa:lossy.networkhexaCan we commit on what the next staging cycle will be?18:03:18
@hexa:lossy.networkhexa25.11 because it is the oldest at this point?18:03:38
@hexa:lossy.networkhexaUnstable? In which case we need the x86-64-darwin drop changes18:04:12
@hexa:lossy.networkhexaTime until 25.11 eol is just above 5 weeks18:08:22
@vcunat:matrix.orgVladimír ČunátI don't know what to choose.18:08:29
@hexa:lossy.networkhexaBest case it gets two more staging cycles18:08:42
@hexa:lossy.networkhexa4 cycles at just under 10 days18:09:48
@vcunat:matrix.orgVladimír ČunátTheoretically we could do 26.05 and then merge the same set of commits to master. They were almost all cherry-picks.18:10:14
@emilazy:matrix.orgemily25.11 seems like a good idea given all the security stuff recently?18:10:17
@hexa:lossy.networkhexa3 cycles at 12.3 days18:10:19
@emilazy:matrix.orgemily and also because it's slightly awkward timing for me wrt x86_64-darwin :P (though I can make it work whenever it happens still) 18:10:47
@emilazy:matrix.orgemilyhow long ago was the last 25.11 cycle?18:10:54
@emilazy:matrix.orgemilyI'd sort of guess that if we do 25.11 it's the last cycle it'll get. conversely I'd guess that if we don't do 25.11 its last cycle will land security updates post-EOL. just a hunch though18:11:26
@hexa:lossy.networkhexaMay 5th 😯18:11:38
@emilazy:matrix.orgemilyso about 2,000 CVEs ago18:11:51
@hexa:lossy.networkhexa Yeah +/- 1500 18:12:13
@vcunat:matrix.orgVladimír Čunát
In reply to @vcunat:matrix.org
Theoretically we could do 26.05 and then merge the same set of commits to master. They were almost all cherry-picks.
Or this after 25.11 cycle.
18:20:26
@emilazy:matrix.orgemily that would mean including x86_64-darwin for that cycle I suppose? 18:20:56
@vcunat:matrix.orgVladimír ČunátI guess.18:21:45
@emilazy:matrix.orgemilywell, can't skip it on 26.05 😅18:22:35
@emilazy:matrix.orgemilywe seem to end up reliably doing those hybrid cycles lately;18:22:49
@emilazy:matrix.orgemily* we seem to end up reliably doing those hybrid cycles lately…18:22:51
@vcunat:matrix.orgVladimír ČunátI took a liking to the associated savings.18:25:57

Show newer messages


Back to Room ListRoom Version: 6