-
-
Notifications
You must be signed in to change notification settings - Fork 16.6k
staging-next 2025-08-10 #432489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
staging-next 2025-08-10 #432489
Conversation
Fixes: 1010b26 ("e2fsprogs: 1.47.2 -> 1.47.3")
PAM switched to meson build upstream, which requires some care: - build with logind support - reenable lastlog - clean up autotools remnants - disable debug as it slows down test making it fail
Co-Authored-by: Marcin Serwin <marcin@serwin.dev>
Conflicts: pkgs/development/python-modules/django-stubs-ext/default.nix pkgs/development/python-modules/django-stubs/default.nix pkgs/development/python-modules/python-roborock/default.nix
…table-2025-04-28 -> 0-unstable-2025-06-19 (#419337)
Remove broken patches. The nspawn conditional can be omitted, as it will not be installed on `systemdLibs` anyways. Testing done: ``` nix why-depends --precise .#systemdMinimal.out .#getent.out /nix/store/x2dhq7nb43xv2c3hh8y7g4bkdzndy7av-systemd-minimal-257.7 └───bin/systemd-nspawn: …valid, ignoring....../nix/store/h5f0zw8gp3fsrzldsi9x2j29gqz6dv4h-getent-glibc-2.40-66/bin/getent… → /nix/store/h5f0zw8gp3fsrzldsi9x2j29gqz6dv4h-getent-glibc-2.40-66 ``` ``` 'git+file:///home/grimmauld/coding/nixpkgs#systemdLibs.out' does not depend on 'git+file:///home/grimmauld/coding/nixpkgs#getent.out' ``` `systemdMinimal`, `systemdLibs`, `pam` all builds. `pkgsMusl.pam` evals successfully.
The `dangerous_implicit_autorefs` lint now causes a compile error [1], which breaks pgvecto-rs. This commit forces the lint to only throw a warning. [1]: rust-lang/rust#141661
This reverts commit 89af1fa. https://hydra.nixos.org/build/305213285/nixlog/2/tail I tried applying a patch, but that wouldn't fix the build: explosion/thinc@47d8e1067de1fc994711a55d4d Also note that upstream considers 8.3.6 to be the latest version now: https://github.com/explosion/thinc/releases/latest
https://hydra.nixos.org/build/304767823/nixlog/4/tail I'm not sure why the issue doesn't happen on linux.
|
@vcunat Hi!
|
There are thousands of jobs regressing (by Hydra). The #staging chat participants just felt like it's better to merge already. Insufficient human resources in there to make this better (without delaying the security updates a lot, etc.) |
@vcunat without kitty all others are fine for my system:
|
@vcunat Fantastic job! Thank you! |
Fix in #436106 |
legacyPackages.aarch64-darwin.adios2 failed with a cmake fortran flag test
See https://hydra.nixos.org/build/304577995/nixlog/1 The related cmake source writes
No idea why the test failed on darwin with this staging cycle. BTW, force use of -DADIOS2_USE_Fortran_flag_argument_mismatch=ON do fix build of adios2 on darwin. |
folium and mapclassify are failing. |
IMHO it's better to create a build failure issues to notify the maintainers after merge of staging-next, as it should now follow the "normal" issues flow and also it's more visible for others now. Still linking back to the staging-next pr is helpful. |
Helpful links
https://hydra.nixos.org/job/nixpkgs/staging-next/unstable#tabs-constituents
https://hydra.nixos.org/job/nixos/staging-next-small/tested
https://hydra.nixos.org/jobset/nixpkgs/staging-next
https://hydra.nixos.org/jobset/nixos/staging-next-small
Important breakages
nothing notable so far