-
Notifications
You must be signed in to change notification settings - Fork 892
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
rustup update doesn't give the same info as rustup update [toolchain] #1245
Comments
Interesting, i fixed the disk space thing, now im getting a different error, this one specifically about renaming the directories. Not sure what is going on.
edit: removing the conflicting library fixed it, just not sure why it occurred in the first place. |
This is another instance of missing/corrupt manifest data. Without knowledge of the installed file, rustup cannot remove it prior to installing the updated version, and then hits a conflict due to the file already existing, and you get the error. We've got a bunch of these bugs scattered all over the place, I'm closing them all to bring order. See #2417. The first thing you posted showed the error right before checking for self-updates:
And after that you were in trouble - see the bug I've linked for details. |
Not sure if this is intended or not, but it caused me a bit of confusion for a second.
rustup version:
rustup 1.6.0 (a11c01e8c 2017-08-30)
Example
rustup udpate
:example
rustup update stable
It ended up being that I didn't have enough space (only 300MB left), but getting the info on why an error occurred, even if they are different for different toolchains, would still be helpful.
I haven't tested what it says if you only have one toolchain installed, so I'm not completely sure in that situation; #1243 seems to suggest that it still happens, though.
The text was updated successfully, but these errors were encountered: