-
Notifications
You must be signed in to change notification settings - Fork 13.3k
rustup: 1.31.1 cannot be updated to via rustup on macos #57148
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
Had no problem on mac, but similar problem on Linux for 1.31.1: |
I seem to have been able to update...
|
I rolled the VM image back to what I had earlier today (banzai to the wonders of zfs!)
|
So at least the problem is reproducible, lmk if you need any other specific info to reproduce. |
Hm, okay -- unfortunately I am not on zfs so a similar rollback scheme wouldn't work here. I'm not sure what information would be needed additionally... the PR that caused the failure on nightly is almost certainly not the problem here as it's too recent (merged ~3 days ago)... |
From the output it feels like the root cause is the missing "removing component" part of the upgrade process. |
I'm going to go ahead and close this as I suspect it's extremely rare that this happens given that we haven't had other reports, if it is still a bug. Regardless it's probably in rustup, not the packaging scripts themselves, so should be filed there. |
Similar issue to #57111 affects 1.31.1. Running rustup update fails to update the stable version of the compiler on my macos VM.
On my linux machine no such problem could be reproduced.
The text was updated successfully, but these errors were encountered: