| 16 Nov 2025 |
 Grimmauld (any/all) | FAILED: [code=1] src/gallium/drivers/rocket/libintercept.so.p/intercept.c.o
x86_64-unknown-linux-musl-clang -Isrc/gallium/drivers/rocket/libintercept.so.p -Isrc/gallium/drivers/rocket -I../src/gallium/drivers/rocket -Iinclude -I../include -I/nix/store/375gkn4faf8wchh>
../src/gallium/drivers/rocket/intercept.c:299:1: error: conflicting types for 'ioctl'
299 | ioctl(int fd, unsigned long request, ...)
| ^
/nix/store/incvp6dvjg46nsy55y5d32881pqz1cz5-musl-x86_64-unknown-linux-musl-1.2.5-dev/include/sys/ioctl.h:115:5: note: previous declaration is here
115 | int ioctl (int, int, ...);
| ^
1 error generated.
uh oh, musl mesa is acting up now | 10:48:51 |
 K900 | Could try disabling rocket for now | 10:50:49 |
| K900 | You probably don't need it | 10:50:53 |
| Grimmauld (any/all) | yeah thats a fair assumption | 10:55:51 |
| Grimmauld (any/all) | woohoo, toy VM is running on current staging-next, and apart from that mesa thing i got no regressions | 12:01:54 |
 leona | my desktop also runs on staging-next | 12:02:31 |
 Randy Eckenrode | The curl one? It’s caused by a bug in c-ares that was fixed upstream but hasn’t yet made it into a release. I’d be surprised if it’s very common. I wouldn’t restart staging-next just for that, but if it were getting restarted, I think it’s worth including. If it doesn’t make it, I plan on tagging it for backport to 25.11 to be included in the next cycle. | 14:21:21 |
| K900 | Yeah I don't think we restart | 14:51:58 |
| K900 | Timing is already tight | 14:52:01 |
 Yureka (she/her) | Is there any reason to assume LLVM 21 miscompilations for aarch64 are limited to aarch64-darwin? | 17:28:36 |
| Yureka (she/her) | e.g. https://github.com/NixOS/nixpkgs/issues/453372, https://github.com/llvm/llvm-project/issues/166870 | 17:29:19 |
| Yureka (she/her) | miscompilations on both aarch64-{linux,darwin} would be a pretty good reason to scrap this cycle | 17:30:00 |
 hexa |
21k rebuilds on trunk-combined 🫠
| 19:38:35 |
| hexa | * > 21k rebuilds on trunk-combined 🫠 | 19:38:38 |
| hexa | is that staging-nixos? 🤔 | 19:41:09 |
| K900 | Possible | 19:41:28 |
| hexa | 5.7k nixos tests | 19:41:42 |
| leona | staging-nixos was merged 2 days ago | 19:44:52 |
| leona | so very probably yes | 19:45:07 |
| hexa | fits | 19:45:08 |
| hexa | 
Download image.png | 19:46:39 |
| hexa | restarting the queue runner | 19:46:40 |
 Vladimír Čunát | Also home-assistant and others. I often look at
https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Amerged+label%3A%2210.rebuild-linux%3A+501%2B%22+base%3Amaster+sort%3Aupdated-desc+ | 19:52:49 |
| hexa | I will say that home-assistant PRs generally overlap fairly well | 19:56:58 |
| hexa | since they are mostly rebuilding the home-assistant tests | 19:57:34 |
| hexa | for which I still have no better idea than exposing them as a top-level package, sorry | 19:57:48 |
| hexa | if they become too annoying we can probably drop the from hydra | 19:58:48 |
| hexa | but it is kinda important to have them in nixpkgs-review results | 19:59:01 |
| 17 Nov 2025 |
 mdaniels5757 | Circling back to this: I was able to build this (/nix/store/gs8wmqs9myb336m5z95prbrn26z9vqdh-firefox-unwrapped-145.0 on aarch64-build-box.nix-community.org), but realized I have no way to test (X11 forwarding doesn't seem to be working, and my virtualization plan has failed on me :)). If someone else happens to have an aarch64-linux machine to test on, that probably would be a good idea. (If you have an aarch64-linux machine, but don't have access to the community builder, I can magic-wormhole you a file that you can use with nix copy --from .) | 01:03:47 |
 dotlambda | Is it acceptable to merge a PR causing <8000 (mostly Python) packages to be rebuilt into staging-next?
https://github.com/NixOS/nixpkgs/pull/462435 | 01:55:06 |
