| 16 Nov 2025 |
 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 |
| dotlambda | It's also basically guaranteed to cause no regressions | 01:55:34 |
| dotlambda | The reason for merging into staging-next is that I'm not sure we'll get https://github.com/NixOS/nixpkgs/pull/455889 in before branch-off | 01:59:26 |
| dotlambda | But I'm happy to backport to staging-25.11 instead if that's preferred | 01:59:54 |
| dotlambda | Actually, python313Packages.httpcore (on staging-next) hasn't even been cached by Hydra yet, so this should definitely be fine | 02:06:58 |
| dotlambda | Though python312Packages.httpcore was cached | 02:07:42 |
| dotlambda | In reply to @hexa:lossy.network
if they become too annoying we can probably drop the from hydra I don't see much of a disadvantage in setting hydraPlatforms = [ ] | 02:22:12 |
| dotlambda | Or would that remove them from nixpkgs-review too? | 02:22:34 |
| dotlambda | It would :(
Tested in https://github.com/NixOS/nixpkgs/pull/462445 | 02:35:01 |
|  debtquity joined the room. | 02:54:57 |
