-
Notifications
You must be signed in to change notification settings - Fork 894
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 1.17 complains about not being installed in CARGO_HOME #1742
Comments
Interesting. Are you able to bisect between 1.16.0 and 1.17.0 to find the commit which causes this to occur? I am not really au-fait with docker so don't know how I'd do that myself. |
These were just the docker images I’ve been using in CI so was the easiest way to test without affecting my system, I only have these two versions of rustup installed in them. I can probably give bisecting a go later today. |
Thank you. |
I found some time to do it earlier, first failing commit is 9f532de
which makes sense, the other issues I noticed related to this error message were from running It looks like this can be suppressed with |
Workaround rust-lang/rustup#1742 on rustup 1.17
Interesting, thank you. The --no-self-update option is indeed deliberately hidden, perhaps @nrc can explain why? |
I cannot. I think it should be documented. |
OK, thanks, I'll see if I can get to that if you don't before me. @Nemo157 would that be sufficient for you, or do you think there's a better error we might give in this circumstance? |
That seems fine. You could consider adding some context to the error message so that users know it's self-update related, but this seems like a niche enough use-case. I think the real fix would be decoupling the environment variables that determine where rustup is installed and where cargo caches the registry & crates, but seeing as RFC1615 has been stuck for almost 3 years and it's somewhat related, I don't see that happening anytime soon. |
OK thanks, I'll assign this to myself to remind me to get some documentation around |
Fixes: rust-lang#1742 Signed-off-by: Daniel Silverstone <dsilvers@digital-scurf.org>
On
rustup 1.16.0
it was possible to overrideCARGO_HOME
to change Cargo's cache directory, sincerustup 1.17.0
this has stopped working andrustup
complains about not being installed under the overriddenCARGO_HOME
directory:The text was updated successfully, but these errors were encountered: