-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
musl: 1.2.3 -> 1.2.5 #229439
musl: 1.2.3 -> 1.2.5 #229439
Conversation
#259989 includes the necessary Rust fixes, so will unblock this when merged. |
b1da5ba
to
fdade3e
Compare
1.2.5 is out now, but it doesn't look like anything in that update will be nearly as hard as LFS in 1.2.4, so I'm now aiming to go straight to 1.2.5 with this. Help with reviewing the package fixes (the libselinux one has been open for a while) would be very helpful with getting this moving. |
@yu-re-ka can we keep them all in the big list in the PR body? Otherwise they're going to get hard to keep track of when GitHub starts hiding comments. |
Needed for compatibility with musl 1.2.4+. Link: NixOS#229439
Needed for compatibility with musl 1.2.4+. Link: #229439
There is a PR updating GN here: |
The gn update does not address the LFS64 breakage though |
Unless there are any last minute objections, I intend to merge this with the next staging cycle. (There aren't enough rebuilds to force this into staging, but there are important fixes that are only in staging.) Every package previously identified as regressing on update builds with musl 1.2.5 on staging, with the exception of nfs-utils, which doesn't work on master anyway and hasn't for a while. Merging this is the best way to fix building pulseaudio with musl and GCC 14, and we're also increasingly seeing packages relying on features introduced in later versions of musl — there are two reverts for hacks we've had to do for 1.2.3 in this PR, and I also recently discovered that we need a newer musl for bcachefs-tools. Since we don't have Hydra for musl, there will absolutely be a long tail of broken packages that we can't identify, but it's been a year and a half. This is as good as it's going to get, and we can't hold back forever. |
6689723
to
5a5c127
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
go for it 🎉
5a5c127
to
efcd97f
Compare
From a packaging perspective, this is the most important thing about this upgrade:
Source
I think we should see which packages are affected, and give it some reasonable amount of time for them to be fixed, because I don't think it's going to always be as simple as modifying CFLAGS — what do we do for rustc, for example?
We also have some work ahead of us to even identify broken packages. I've done some test builds of the Spectrum live image, which heavily uses musl, to identify a few regressions, but since we don't have Hydra for musl, we're going to need people who use musl in Nixpkgs to do their own test builds to check whether any of the packages they care about are affected. If you do so, add any more broken packages to the list in this post (or comment if you lack permissions).
fuse2 (issue in fuse headers manifests in e2fsprogs after updating) (Void patch)no other package seems to have that problem, and e2fsprogs is fixed now.New! with GCC 14
Where we can fix things without breaking things for musl 1.2.3, let's apply those fixes in separate PRs, so the work can be more easily spread out, and avoid this one becoming intimidatingly huge.
Resources