-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Beta cargo update failing with "object not found - no match for ID" #8705
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
If you solved this, please let me know. I'm facing the same issue myself. |
I did but I wish I'd written down how. I seem to remember it going away after a |
I was getting this error and was able to resolve it by removing the 'registry' directory under ~/.cargo The next time I ran cargo, it refetched and rebuilt packages/crates from scratch. |
Transferred to the cargo repository. This sounds like #3561 has maybe returned? |
I think this is a duplicate of #4007, so closing in favor of that. If any of you still have the problem, can you compress |
I was getting this:
Wiping $HOME/.cargo/registry fixed the issue. Here's the contents of registry/anyhow*: |
@asayers Thanks for sending the snapshot. Unfortunately the part that is needed is the entire |
Oh, sorry - it's already gone! 😞 |
This is on the latest beta:
I've seen previous issues about cargo not correctly handling changed dependencies, could this be related? I'm going to zip my .cargo and .rustup, let me know if they'd be useful and what the best way to send them would be.
Platform is Windows 10's Debian WSL, i.e. unknown-linux-gnu
The text was updated successfully, but these errors were encountered: