-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Can't build cargo-c due to dependency problems in cargo #15387
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
Comments
This also affects cargo-outdated and probably everything else depending on |
It is probably due to: 6ec8da9 via #15168. the Repro: git switch -d origin/rust-1.86.0
cargo semver-checks -p cargo-util-schemas --baseline-version 0.7.2 @obi1kenobi I guess the tracking issue of catching type changes is obi1kenobi/cargo-semver-checks#1005? |
Plan to mitigate SemVer violations:
See the release process: https://doc.crates.io/contrib/process/release.html#cratesio-publishing. |
This is needed because a type of public field has changed but was overlooked and was SemVer breaking. See rust-lang#15387
### What does this PR try to resolve? This is needed because a type of public field has changed but was overlooked and was SemVer breaking. See also * #15387 (comment) * [#t-cargo > [email protected] SemVer Violations](https://rust-lang.zulipchat.com/#narrow/channel/246057-t-cargo/topic/cargo-util-schemas.400.2E7.2E3.20SemVer.20Violations) These commit are cherry-picked in order to make CI happy: * 62bd1ad * 9946566 * 251a078
New versions are just dropped! Kudos to the Rust Release Team! And thanks everyone for your reporting! |
Problem
Can't do a bootstrap, because it returns an error when building cargo-c. It returns a compiling error. Seems to be either a bug in cargo's dependencies, not being strict enough, or one of the dependencies breaking the API without updating versions accordingly. This is the full output:
Steps to reproduce
Notes
This is part of a snapcraft build recipe. It has been working fine for months, every time we rebuilt the snap, but yesterday began to fail. I tested it manually on my computer, typing the commands manually on a prompt, and failed too, when it worked fine months ago.
A workaround was commented in the cargo-c repository, consisting on adding
--locked
. It seems to work.Version
The text was updated successfully, but these errors were encountered: