!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
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)(did i say i find the libxml-native testsuite quite lacking?)21:37:41
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)there is a reason why my goal was to build towards libreoffice21:38:11
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)the open document formats are basically xml, and pull all the fun svg and html stuff in deps21:38:29
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)LO has actually good tests, but building towards it sucks21:39:00
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)i mean i also had to patch like three other things. Two of those were const-ness issues, where fields either became const or lost their const. Thats dumb api breakage for very little reason...21:42:04
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)truly not a fun update21:42:14
@elvishjerricco:matrix.orgElvishJerricco

https://github.com/NixOS/nixpkgs/pull/444946

I only just realized that since it only affects musl it probably doesn't need to target staging, is that right Alyssa Ross? (But if it does need to, it probably should be staging, not staging-next at this point?)

22:45:15
22 Sep 2025
@qyliss:fairydust.spaceAlyssa RossYeah that's fine for master04:56:04
@k900:0upti.meK900So uh05:23:41
@k900:0upti.meK900Did anyone get the dotnets05:23:45
@k900:0upti.meK900I think I'm down to that and like three other things now05:24:06
@k900:0upti.meK900And I have a new candidate for biggest commit with cmake 4 fixes hidden in it: https://github.com/SoftFever/OrcaSlicer/commit/883607e1d4a0b2bb719f2f4bcd9fd72f8c2174fa05:32:58
@k900:0upti.meK900Oh god I found the dotnet expression05:46:52
@winter:catgirl.cloudWintercondolences05:48:49
@k900:0upti.meK900OK I think I figured out how to shove the patch in there06:21:54
@k900:0upti.meK900OK I think this actually does work06:38:54
@ofalvai:matrix.orgofalvai To be honest, I was building off a few days old staging and encountered the failure there. But now I see the failure in Hydra as well: https://hydra.nixos.org/build/308144224 06:42:30
@vcunat:matrix.orgVladimír ČunátThe error doesn't happen on x86_64-linux, so that can be confusing.06:47:02
@k900:0upti.meK900
/build/dotnet-9.0.110/eng/detect-binaries.sh: line 135: 5091 Segmentation fault /build/dotnet-9.0.110/.dotnet/dotnet run --project /build/dotnet-9.0.110/eng/tools/BinaryToolKit -c Release --property:RestoreSources=/nix/store/pir670rnvffbwf5jigw5zgm5c442z8px-dotnet-stage0-sdk-9.0.110-artifacts clean /build/dotnet-9.0.110 -o /build/dotnet-9.0.110/artifacts/log/binary-report -ab /build/dotnet-9.0.110/eng/allowed-sb-binaries.txt -l Debug -p CustomPackageVersionsProps=/nix/store/pir670rnvffbwf5jigw5zgm5c442z8px-dotnet-stage0-sdk-9.0.110-artifacts/PackageVersions.props
07:01:53
@k900:0upti.meK900So uhhh07:01:55
@k900:0upti.meK900Maybe we pin LLVM 20 lol07:01:59
@k900:0upti.meK900I'm going to try building it with LLVM 20 pinned07:11:56
@k900:0upti.meK900Well at least it doesn't just immediately segfault this time07:48:35
@k900:0upti.meK900OK yeah it definitely does not segfault on 2008:10:26
@k900:0upti.meK900So does anyone want to figure this out08:18:20
@k900:0upti.meK900Or should I just send it08:18:23
@k900:0upti.meK900Because it definitely works on 2008:18:28
@k900:0upti.meK900And it definitely doesn't on 2108:18:31
@vcunat:matrix.orgVladimír ČunátI'd say you send it. That won't prevent anyone from fixing it at any point in the future.08:22:16
@k900:0upti.meK900I'm going to let it finish building EVERYTHING just to be super sure08:23:15

Show newer messages


Back to Room ListRoom Version: 6