-
Notifications
You must be signed in to change notification settings - Fork 94
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
Some crates.io hashes cannot be found in Cargo.lock #370
Comments
You are bumping into this issue because, most likely, you have git dependency in The solution is to run |
@danieldk Thanks! I'll try that. I suppose then that I should re-run |
Hi! I found that this error can occur if you have a dependency that uses the v1 Cargo.toml manifest format. That format has a I agree that git dependencies can also cause this type of error. But looking at the dependency names in the error message you can see all of the names begin with "a". The error output shows the first 10 dependencies with missing checksums in alphabetical order. When you encounter a lock file where crate2nix couldn't find checksums for any dependency you see a lot of "a" names in the error message like in this case. That makes me think this is a v1 manifest problem. |
I'm running into this:
It's difficult to make a minimal reproduction but just in case is it a known error? I tried running
cargo update
but that doesn't change anything.The text was updated successfully, but these errors were encountered: