Skip to content
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

Yank libc 0.1.0 to 0.1.4 #2641

Closed
KamilaBorowska opened this issue Jan 21, 2022 · 3 comments
Closed

Yank libc 0.1.0 to 0.1.4 #2641

KamilaBorowska opened this issue Jan 21, 2022 · 3 comments

Comments

@KamilaBorowska
Copy link

libc versions 0.1.0, 0.1.1, 0.1.2, 0.1.3 and 0.1.4 don't compile anymore. This makes it more annoying to use cargo update -Z minimal-versions. Could those versions be yanked? This won't affect ancient versions of Rust, as I doubt those versions are capable of using crates.io-index nowadays.

@JohnTitor
Copy link
Member

I'm fairly sure that these old versions aren't used now but also doubt if it's worthwhile to yank them just for one nightly feature.

@dekellum
Copy link

I agree its not worthwhile. IMO, Better to fix minimum allowed libc in all (transitive or direct) dependencies where it violates those MSRVs. This failure to set appropriate minimums is of course exacerbated by the fact that libc has failed to release a 1.0, see #547 (comment).

@JohnTitor
Copy link
Member

Closing in favor of the above reasons, thanks for reporting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants