!UNVBThoJtlIiVwiDjU:nixos.org

Staging

317 Members
Staging merges | Find currently open staging-next PRs: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+sort%3Aupdated-desc+head%3Astaging-next+head%3Astaging-next-21.05+is%3Aopen109 Servers

Load older messages


SenderMessageTime
21 Sep 2025
@k900:0upti.meK900 If it comes to that 05:46:42
@vcunat:matrix.orgVladimír ČunátThese packages are all huge rebuilds.05:46:48
@elvishjerricco:matrix.orgElvishJerriccoRight well my question is: Is the next cycle allowed to contain changes to systemd if it won't be merged to master until after 2025-10-04?05:47:36
@vcunat:matrix.orgVladimír ČunátThe date is about merges to staging.05:48:00
@elvishjerricco:matrix.orgElvishJerriccoahh05:48:04
@vcunat:matrix.orgVladimír Čunát And 2025-10-04 looks like about exactly when the next staging-next will start. 05:48:23
@vcunat:matrix.orgVladimír Čunát * And 2025-10-04 looks like about exactly when the next staging-next might start. 05:48:33
@elvishjerricco:matrix.orgElvishJerriccoOk, so 2025-10-04 is my deadline for this stuff; which is further out than I was planning on taking.05:48:51
@elvishjerricco:matrix.orgElvishJerriccoso I should be all good pretty easily05:49:05
@vcunat:matrix.orgVladimír ČunátIt's certainly good that disruptive changes get merged at least a few weeks before the stable release.05:49:49
@elvishjerricco:matrix.orgElvishJerriccoYea I had intended to have initrd by default done like a month ago but time got away from me :/05:50:21
@k900:0upti.meK900 I'm building staging-next locally 07:38:58
@k900:0upti.meK900 Since I've got cycles to burn 07:39:10
@k900:0upti.meK900 Pushed a fix for dht 08:08:00
@k900:0upti.meK900https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/by-name/ya/yajl/package.nix#L3108:13:39
@k900:0upti.meK900Yay 10 year old JSON parser08:13:44
@k900:0upti.meK900Very barely more alive fork at https://github.com/containers/yajl08:15:42
@k900:0upti.meK900 @emily thoughts? 08:17:57
@k900:0upti.meK900(I know you enjoy these kinds of things)08:18:30
@k900:0upti.meK900The funny thing is, the fork doesn't even change08:23:48
@k900:0upti.meK900* The funny thing is, the fork doesn't even change the cmake version08:23:51
@k900:0upti.meK900But it does have other fixes we probably want08:23:58
@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

Show newer messages


Back to Room ListRoom Version: 6