!UNVBThoJtlIiVwiDjU:nixos.org

Staging

372 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/122 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
7 Mar 2026
@dramforever:matrix.orgdramforever and then uh, does something 11:44:41
@yuka:yuka.devYureka (she/her)it builds different objects depending on what /proc/cpuinfo you have during the build11:44:52
@dramforever:matrix.orgdramforever if dynamicArch means runtime that's good 11:44:58
@dramforever:matrix.orgdramforeveruh oh11:45:04
@k900:0upti.meK900 I think dynamicArch does mean runtime 11:45:06
@yuka:yuka.devYureka (she/her)hmm11:45:17
@k900:0upti.meK900 But it ALSO tries to be smart somehow 11:45:15
@yuka:yuka.devYureka (she/her)so maybe both11:45:19
@yuka:yuka.devYureka (she/her)why would my different build hosts fail with different errors then?11:45:39
@dramforever:matrix.orgdramforever but it is passing different -march to different objects 11:45:39
@dramforever:matrix.orgdramforeverso something is going on11:45:43
@k900:0upti.meK900That postPatch line is also hella sus11:46:00
@k900:0upti.meK900 In the nixpkgs PR change 11:46:06

Show newer messages


Back to Room ListRoom Version: 6