-
Notifications
You must be signed in to change notification settings - Fork 83
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
Unable to compile v0.28.0 #1771
Comments
I'm also seeing this behavior: it's causing my CI runs to fail. |
Also seeing this. |
For stable installs you should always use the |
Unlocked installs are the default because it allows semver compatible dependency upgrades (for bug fixes etc). Cargo still publishes lockfiles to ensure reproducible builds and in case dependencies break (ie. exactly this situation). For CI builds it is a good idea to do locked installs (or use Regardless, a broken unlocked build indicates a dependency made a breaking change, a semver violation. I filed this issue because the violation should be tracked down. Saying "just do a locked install" avoids the underlying problem and does nothing to prevent it from happening again. https://doc.rust-lang.org/cargo/commands/cargo-install.html#dealing-with-the-lockfile |
I agree, I was specifically responding to the post about it breaking CI. |
I've got this problem as well - maybe I'm obtuse, but is there a workaround that I missed? |
cargo install cargo-dist@0.28.0 --locked |
That definitely solved my CI issue. |
Thank you, that works! |
cargo install cargo-dist@0.28.0
:The issue seems to be related to the target-lexicon crate.
The unlocked build compiles both
target-lexicon
versions 0.12.16 AND 0.13.2, but the --locked install (which works) only builds v0.12.16.Cloning the current repo, running
cargo update
and thencargo build
fails with the same error.Before:
After:
Output of running cargo update
The text was updated successfully, but these errors were encountered: