-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
latest libc doesn't build on 1.47 #2866
Labels
C-bug
Category: bug
Comments
I just ran into this as well (on 1.48, FWIW). It looks like an issue with packaging potentially due to this rust-lang/cargo#10954. |
According to that bug its just an issue on nightly? So presumably whoever uploaded the latest libc just needs to do a bump+reupload using stable cargo, not nightly? |
Yes that's my understanding of the issue as well. |
I've yanked v0.2.128, will make a new release soon. |
JohnTitor
added a commit
to JohnTitor/libc
that referenced
this issue
Aug 9, 2022
... because v0.2.128 has a Cargo bug: rust-lang#2866 Signed-off-by: Yuki Okushi <jtitor@2k36.org>
Merged
bors
added a commit
that referenced
this issue
Aug 9, 2022
Bump up to v0.2.129 ... because v0.2.128 has a Cargo bug: #2866 Signed-off-by: Yuki Okushi <jtitor@2k36.org>
Merged
Merged
libguestfs
pushed a commit
to libguestfs/nbdkit
that referenced
this issue
Nov 1, 2022
This reverts commit 539ee34. This was a workaround for an upstream bug, but upstream has now fixed the bug. See rust-lang/libc#2866
libguestfs
pushed a commit
to libguestfs/nbdkit
that referenced
this issue
Nov 18, 2022
This reverts commit 539ee34. This was a workaround for an upstream bug, but upstream has now fixed the bug. See rust-lang/libc#2866 (cherry picked from commit dc55cac)
tatref
pushed a commit
to tatref/libc
that referenced
this issue
Mar 20, 2023
... because v0.2.128 has a Cargo bug: rust-lang#2866 Signed-off-by: Yuki Okushi <jtitor@2k36.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looks like all our CI jobs are now failing with:
The text was updated successfully, but these errors were encountered: