!UNVBThoJtlIiVwiDjU:nixos.org

Staging

359 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
18 Apr 2026
@jkarlson:kapsi.fiEmil Thorsøenot insurmountable though15:15:47
@k900:0upti.meK900There's a whole bunch of issues really15:16:15
@vcunat:matrix.orgvcunatUh, the autoconf update is such a PITA for darwin.21:53:46
@vcunat:matrix.orgvcunatToo many packages break from getting autoreconf-ed with -std=gnu2321:54:04
@vcunat:matrix.orgvcunatMany packages just aren't ready for such new stuff.21:54:33
@vcunat:matrix.orgvcunatI hate that C standard even does get changed by autoreconfig. It doesn't make sense. Only upstream should switch that.21:57:05
@vcunat:matrix.orgvcunat* I hate that C standard even does get changed by autoreconf-ing. It doesn't make sense. Only upstream should switch that.21:57:23
19 Apr 2026
@qyliss:fairydust.spaceAlyssa RossOnly upstream is supposed to run autoreconf06:16:08
@qyliss:fairydust.spaceAlyssa RossThat's the design.06:16:11
@vcunat:matrix.orgvcunatI know, but not everyone agrees with that. And sometimes you need to apply patches which may make it hard to avoid it.07:57:20
@qyliss:fairydust.spaceAlyssa RossYep, and if we do that, we're opting into keeping up with autoconf changes and should be taking that into consideration.08:01:35
@qyliss:fairydust.spaceAlyssa RossIt's also changed by new compiler versions by default, right? So even without autoconf it's not solely on upstream.08:05:44
@qyliss:fairydust.spaceAlyssa Ross What we can do is make sure every time we have to pin a C standard, we send that change upstream so going forward upstream will take responsibility for it 08:07:37
@vcunat:matrix.orgvcunatWe could. But that's even increasing the amount of work that we need to do.08:10:57
@vcunat:matrix.orgvcunatLike, I'm not really motivated to spend many hours on this, especially as it doesn't even affect Linux.08:12:03
@vcunat:matrix.orgvcunat* Like, I'm not really motivated to spend many hours on this, especially as it doesn't even affect Linux (currently).08:12:12
@qyliss:fairydust.spaceAlyssa RossSure, not saying you should.08:12:31
@qyliss:fairydust.spaceAlyssa RossWe have the big darwin-maintainers team for issues like this, I think08:12:47
@vcunat:matrix.orgvcunatBut I don't want to block staging-next either or merge it with very large regressions.08:12:48
@qyliss:fairydust.spaceAlyssa RossOur contributor base is quite good at mass stuff like this IME if they're given clear instructions.08:13:38
@qyliss:fairydust.spaceAlyssa RossIf you link me an example on Hydra I could write up an issue.08:14:03
@qyliss:fairydust.spaceAlyssa RossThe burden of this sort of thing shouldn't just be on a few people doing everything08:15:17
@qyliss:fairydust.spaceAlyssa RossWhy is it only for macOS? LLVM update?08:20:22
@qyliss:fairydust.spaceAlyssa Ross * 08:21:10
@vcunat:matrix.orgvcunatIt's possible that it's about clang vs. gcc.08:29:27
@qyliss:fairydust.spaceAlyssa RossThe autoconf release notes say it uses c23 "when available"08:29:39
@qyliss:fairydust.spaceAlyssa Rossso I'd guess that for some reason it's newly available for Darwin specifically, which probably means Clang specifically?08:29:59
@qyliss:fairydust.spaceAlyssa RossYeah I can reproduce one of them from Hydra with pkgsLLVM08:30:15
@qyliss:fairydust.spaceAlyssa RossThat's also good — macOS is not necessarily required to fix08:31:11
@vcunat:matrix.orgvcunatExamples I saw now (because many jobs depend on them): https://hydra.nixos.org/build/326635250 https://hydra.nixos.org/build/32621952508:32:37

Show newer messages


Back to Room ListRoom Version: 6