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
base: staging
Are you sure you want to change the base?
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. |
I opened #313439 didn't see it -- will close. |
is there a Nix cache for musl ? |
There is no official cache for musl. |
Would be cool to cook up an update script also for this. |
Let me know how I can help. I ran into issues building open office for musl due to NULL being #define as nullptr from this patch series -- figured I'd see if we were trying to upgrade first. Let me know how I can help. |
Find packages that currently build, but don't build with this PR applied. (Or if you can't find any, let me know, that's also good data.) |
Does nixpkgs with musl (non-static) even build at 1.2.3 ? Is there a separate musl room on matrix or discord? |
@alyssais I'll start a running list in this thread: Trying to build openmpi
Trying to build libreoffice
|
This isn't the place to collect a list of all packages that fail to build with musl. We're specifically interested in packages that do build with musl on current Nixpkgs, but fail with this PR applied. What you have posted look like packages that are already failing with musl, which are irrelevant for the purpose of upgrading. |
Some rust programs are still broken?
|
Ah, all these programs need to bump their |
Submitted deps bump upstream: https://git.deuxfleurs.fr/Deuxfleurs/wgautomesh/pulls/7 |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@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. |
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).
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