-
Notifications
You must be signed in to change notification settings - Fork 893
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
Cannot update to 1.15 #939
Comments
Thanks for the report @Nemo157. I have a hunch of what happened here, and am hopeful it won't happen again. Need further investigation. |
@brson Status? |
I still have not touched my stable toolchain since I reported this, just tried again in case something changed between rustup 1.0 and now, still get the same error message
still willing to run any kind of debugging commands if anyone has some. |
I had a similar problem when trying to update I solved it by removing the manifest file of the component that had the conflict (in my case After this |
I am having a similar issue installing 1.33.0-nightly (f960f377f 2018-12-24) alongside a fresh installation of 1.31.1-stable (b6c32da9b 2012-12-18) on target x86-64-unknown-linux-gnu.
Output of
Output of
|
The file |
Main issue is #1590. Current workaround is |
With using I get same problem. |
Hah, well I used |
This happened for me as well on my Windows device just now, trying to update to latest stable. Even after restarting the computer (which pretty much works for fixing anything) the error occurred. I ended up deleting all of the folders in the toolchain directory, then running the update process again. Success! |
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. |
rustup update stable
is currently failing for meI also tried a
rustup self update
before trying again and got the same result, versions I tried on wereThis is updating from
In case this was related to some really old rust install I checked if I had this file anywhere else, but it's only in
rustup
managed installs and therust
source:I've been able to update many times in the past, so not sure what's different about this release. I also just updated beta to 1.15.0-beta.5 a couple of days ago fine.
I normally develop on nightly anyway, so I'll leave stable as is in case someone has any debugging commands I could run.
The text was updated successfully, but these errors were encountered: