-
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
Re-running rustup-init deletes multirust directory instead of migrating it #848
Comments
n.b. This is discovered on my MIPS64 box, where there's presently no other way to update |
Thanks for the report. Looking into it. |
brson
added a commit
to brson/rustup.rs
that referenced
this issue
Dec 15, 2016
bors
added a commit
that referenced
this issue
Dec 15, 2016
Upgrade ~/.multirust correctly from rustup-init Fixes #848 r? @alexcrichton
bors
added a commit
that referenced
this issue
Dec 16, 2016
Upgrade ~/.multirust correctly from rustup-init Fixes #848 r? @alexcrichton
nodakai
pushed a commit
to nodakai/rustup.rs
that referenced
this issue
Apr 23, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is definitely caused by #830, although I haven't looked closely into the patch. This would affect those people who:
rustup-init
when there's an update, orrustup-init
in the meantime (although this group may be small).Steps to repro (assuming you're already on
.rustup
):This is likely due to the unconditional
create_rustup_home
which ultimately deleted the legacy rustup home during symlinking. We should perform the migration before proceeding with home creation.The text was updated successfully, but these errors were encountered: