!UNVBThoJtlIiVwiDjU:nixos.org

Staging

355 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/113 Servers

Load older messages


SenderMessageTime
4 Apr 2026
@emilazy:matrix.orgemilyhm? don't you just need to dismiss the review?12:21:32
@emilazy:matrix.orgemilyoh it's a hard failure?12:21:50
@emilazy:matrix.orgemilyI didn't realize that. that should probably be changed, it should never be necessary to bypass the rules unless something is broken...12:22:15
@emilazy:matrix.orgemilywill try remember to open an issue about it12:22:23
@emilazy:matrix.orgemilyopened https://github.com/NixOS/nixpkgs/issues/50664214:32:46
6 Apr 2026
@hexa:lossy.networkhexaI think we should start staging-next in the next few hours16:08:23
@k900:0upti.meK900Someone needs to go through the other PRs16:12:44
@k900:0upti.meK900I think we have security16:12:50
@hexa:lossy.networkhexaI'm going through the PR queue already16:25:35
@hexa:lossy.networkhexabut someone else can do that too16:25:39
@hexa:lossy.networkhexaok, went through the PR queue and merged a bunch of thijngs18:42:44
@hexa:lossy.networkhexaRedacted or Malformed Event18:42:48
@hexa:lossy.networkhexaif you want anything to land, merge it in the next 90 minutes18:43:26
@hexa:lossy.networkhexaRedacted or Malformed Event18:43:30
@k900:0upti.meK900Do we want to send glibc 2.4318:58:40
@vcunat:matrix.orgvcunatIt would have lost of regressions surely.19:00:17
@vcunat:matrix.orgvcunat* It would have lots of regressions surely.19:00:22
@leona:leona.isleonai mean now would be one of the last times where it's possible to do regarding release schedule19:00:24
@k900:0upti.meK900 @ma27 thoughts? 19:16:51
@ma27:nicht-so.sexyma27

NACK from me: this is a glibc release that has notable changes in its C headers meaning it will take a while until projects catch up, whenever this happened for the past few releases, it took me several rounds to get the amoutn of regressions down to a reasonable number. So far we have 1400 new fails on x86_64 (compared to current staging-next - I'm aware that the comparison isn't perfect since the glibc 2.43 branch isn't based of last staging-next, this is a rough estimate, but it's the only somewhat reasonable data point I have right now) with 40% of x86_64 built only. On that base I'd not merge it.

I know it's a bummer for Philip Taron (UTC-8) who wanted to see clang build support land, but I oppose rushing an update of such a core library (and honestly, minor glibc releases are rather major releases given the work I had to put into them in the past 6.5 years).

19:43:49
@k900:0upti.meK900FWIW glibc explicitly does not do semver19:49:58
@k900:0upti.meK900So their "minor" releases are not required to follow the semver definition of "minor release"19:50:15
@ma27:nicht-so.sexyma27sure, I'm aware. just making clear for other readers that 2.43 isn't as small as it might sound.19:51:31
@vcunat:matrix.orgvcunatABI-wise semver maybe19:51:32
@vcunat:matrix.orgvcunat* ABI-wise semver maybe (but that's not much relevant to us)19:51:45
@hexa:lossy.networkhexastdenvs are still stdenving21:00:15
@hexa:lossy.networkhexaRedacted or Malformed Event21:01:00
@hexa:lossy.networkhexa they will keep building until morale improves 21:01:17

There are no newer messages yet.


Back to Room ListRoom Version: 6