!UNVBThoJtlIiVwiDjU:nixos.org

Staging

337 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/111 Servers

Load older messages


SenderMessageTime
18 Jan 2026
@reckenrode:matrix.orgRandy Eckenrodehttps://github.com/NixOS/nixpkgs/pull/481408 fixes it on staging-next.20:30:17
@vcunat:matrix.orgvcunatWhy not tag it as backport-release-25.11 directly?20:34:53
@isabel:isabelroses.comisabel changed their profile picture.20:43:58
@arianvp:matrix.orgArianHeya I'm super confused https://github.com/NixOS/nixpkgs/pull/475079 was opened on 29.12.2025 and merged on 10.01.2026 https://github.com/NixOS/nixpkgs/pull/474788 was merged on 28.12.2025 the 258.3 bump still didn't land on 25.11 Did I miss the window by a few seconds?22:05:22
@arianvp:matrix.orgArianAt this rate , given that the next staging-next-25.11 iteration will take at least a week; it means it'll take ~5 weeks from merge to landing in a channel. That feels long. What could I have done differently to speed this up? Should I have proactively asked to include it in the previous staging-next cycle manually?22:15:48
@arianvp:matrix.orgArian* At this rate , given that the next staging-next-25.11 iteration will take at least a week; it means it'll take ~5 weeks from merge to landing in a channel. That feels way too long. What could I have done differently to speed this up? Should I have proactively asked to include it in the previous staging-next cycle manually?22:15:58
@hexa:lossy.networkhexamake sure we have more people fixing darwin problems22:26:52
@hexa:lossy.networkhexaand prune nixpkgs22:26:59
@mdaniels5757:matrix.orgmdaniels5757You missed it by either a day or a few hours, depending on whether you are counting from https://github.com/NixOS/nixpkgs/pull/475079/changes/847f6e97a3b8eb3d0ee39b035468fecb9b2d1cf6 or https://github.com/NixOS/nixpkgs/pull/475079/changes/488bd0cc3f63fab0c24c69dfeff2db38d8a3e9f1.22:28:45
@grimmauld:m.grimmauld.deGrimmauld (any/all)can we make non-minimal systemd somehow not a mass-rebuild maybe? systemdMinimal and systemdLibs will always go to staging, but i wonder if the big systemd has to.22:28:51
@hexa:lossy.networkhexaif you want it in it's best to talk to people in this room22:30:06
@hexa:lossy.networkhexamissing a cycle is expensive indeed22:30:16
@hexa:lossy.networkhexathere are options to delay the start of a cycle or merge things into an active cycle22:32:53
@joerg:thalheim.ioMic92I wonder if we can convince upstream to restructure systemd into meson submodules. It's also not nice for normal package managers to have dependency cycles 22:33:53
@arianvp:matrix.orgArian hot take. maybe we should only support darwin on unstable and not on the release branches. Those release branches are for NixOS after all. Having NixOS updates delayed because of darwin feels backwards 23:03:40
@winter:catgirl.cloudWinterdidn’t we have release branch jobsets for darwin23:04:52
@arianvp:matrix.orgArianyeh we have https://hydra.nixos.org/jobset/nixpkgs/nixpkgs-25.11-darwin but we don't have a separate staging-25.11 flow for just darwin iirc?23:06:13
@fabianhjr:matrix.orgFabián Herediahttps://hydra.nixos.org/build/318935477 Can someone cancel this build? Seems to be stuck printing OOM in the tail, been running for 15 hrs :C23:13:27
@emilazy:matrix.orgemily huh? nixpkgs-YY.MM-darwin exists 23:18:50
@emilazy:matrix.orgemilythere are lots of users of stable branches on Darwin23:19:03
@hexa:lossy.networkhexaRedacted or Malformed Event23:27:20
19 Jan 2026
@reckenrode:matrix.orgRandy EckenrodeI didn’t think that would work for some reason.00:19:11
* @reckenrode:matrix.orgRandy Eckenrode raises his hand.00:20:41
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)This applies a fix to nix 2.33 with glibc 2.42 https://github.com/NixOS/nixpkgs/pull/481478 and also disables flaky aarch64-darwin tests since we haven’t come to a good resolution. I’ll try go get around ~tomorrow to sensing those to 25.11 too01:23:50
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)* This applies a fix to nix 2.33 with glibc 2.42 https://github.com/NixOS/nixpkgs/pull/481478 and also disables flaky aarch64-darwin tests since we haven’t come to a good resolution. I’ll try go get around ~tomorrow to sending those to 25.11 too01:24:25
@fabianhjr:matrix.orgFabián HerediaThis should fix some of the breakage on staging-next related to glibc 2.42: https://github.com/NixOS/nixpkgs/pull/48150302:29:11
@fabianhjr:matrix.orgFabián HerediaCurrently building02:29:18
@vcunat:matrix.orgvcunat

there are lots of users of stable branches on Darwin

So far I don't see anyone complaining that it lags on a 10 days old commit. (because issues in Nix itself)

07:06:49
@vcunat:matrix.orgvcunat It's not really possible to separate staging* for the platforms. We only have one master branch and one release-25.11 branch. 07:07:55
@vcunat:matrix.orgvcunatAnd changing that approach would seem really complicated.07:08:20

There are no newer messages yet.


Back to Room ListRoom Version: 6