!UNVBThoJtlIiVwiDjU:nixos.org

Staging

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

Load older messages


SenderMessageTime
21 Sep 2025
@elvishjerricco:matrix.orgElvishJerriccoactually, I guess I could PR the patch that systemd initrd needs right now if that means we can get it in staging-next today, which would let me finish off systemd-initrd-by-default over the next days. Does that work?08:25:32
@k900:0upti.meK900I think we should hold off08:25:50
@k900:0upti.meK900This cycle is already very cursed08:25:56
@elvishjerricco:matrix.orgElvishJerriccoah alright08:26:01
@k900:0upti.meK900We have cmake 4 and LLVM 208:26:08
@k900:0upti.meK900* We have cmake 4 and LLVM 2108:26:09
@k900:0upti.meK900I would REALLY like to not add a systemd update into the mix08:26:24
@elvishjerricco:matrix.orgElvishJerriccothe benefit of doing it this cycle is just that systemd initrd would benefit from more people using it sooner before release, but it's not that big a deal08:26:37
@elvishjerricco:matrix.orgElvishJerricco(well, the systemd "update" would just be a small patch to the shutdown code)08:27:13
@elvishjerricco:matrix.orgElvishJerricco(i'm not talking about 258 right now)08:27:25
@k900:0upti.meK900Oh08:27:29
@k900:0upti.meK900Ehhh08:27:35
@elvishjerricco:matrix.orgElvishJerriccostill just don't want to introduce systemd-initrd-by-default in this cycle? That's fine08:28:28
@k900:0upti.meK900I am at this point genuinely just afraid of touching it lol08:28:54
@k900:0upti.meK900(outside of fixing cmake 4)08:28:59
@elvishjerricco:matrix.orgElvishJerriccolol ok08:29:30
@ofalvai:matrix.orgofalvaiSmall fix for toml11 and LLVM 21: https://github.com/NixOS/nixpkgs/pull/44490109:03:41
@k900:0upti.meK900OK there's a lot09:54:16
@k900:0upti.meK900Of cmake 4 fails09:54:24
@k900:0upti.meK900And I'm not even close to done09:54:34
@vcunat:matrix.orgVladimír ČunátShould we call an early ZHF for staging-next this time? 😁11:03:04
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)there is still libxml that'll break shit11:46:28
@vcunat:matrix.orgVladimír ČunátI don't expect we even need it in 25.11 when it comes to it.11:47:26
@vcunat:matrix.orgVladimír Čunát* I don't expect we even need libxml2 2.15 in 25.11 when it comes to it.11:47:53
@vcunat:matrix.orgVladimír Čunát2.13 is still getting security fixes apparently, so I expect 2.14 can hold for several more months.11:48:36
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)we are manually backporting them, and only because there is things that insist on the old ABI11:52:02
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)if it were me we'd have dropped that long ago11:52:13
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)i do NOT want to repeat this backport hell on 25.1111:52:22
@vcunat:matrix.orgVladimír Čunát 2.13 is getting security fixes upstream 11:52:48
@vcunat:matrix.orgVladimír ČunátReleased about a week ago: https://gitlab.gnome.org/GNOME/libxml2/-/commit/04af2cabb9f859c198b8a553c028a8748119941011:53:15

Show newer messages


Back to Room ListRoom Version: 6