-
-
Notifications
You must be signed in to change notification settings - Fork 18k
staging-next 2023-01-05 #209180
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 2023-01-05 #209180
Conversation
All three versions are the same in this respect. It's the issue with old libgcc_s propagated via our glibc package; e.g. #209113
...into staging-next
pipewire: 0.3.63 -> 0.3.64
Got broken due to limitations of the python bulk updater
nodejs: 14.21.1 -> 14.21.2, 16.18.1 -> 16.19.0, 18.12.1 -> 18.13.0, 19.2.0 -> 19.4.0
|
Most failed packages at this point are due to recursing into python311.pkgs, which will receive fixes over the next weeks and months, as libraries are catching up. |
|
Perhaps EDIT: I forgot to say that Hydra reproduced that multiple times and on my machine it wouldn't reproduce at all over multiple attempts. It might be due to emulation on aarch64, but I'm just guessing. |
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