"error: toolchain 'nightly-foo' is not installed" is confusing

[brson]

This "not installed" message happens when the toolchain parser fails to parse the name and then considers it a "custom" toolchain. After that, the operation fails, and the reason is because there is no custom toolchain with that name.

It's confusing though because the user may have typo'd a channel name, not expecting it to be installed.

[Hoverbear]

This is happening with curl https://sh.rustup.rs -sSf | sh as well on Arch Linux 64bit.

[brson]

@Hoverbear it happens at install time on arch? That's weird...

[Hoverbear]

Yes it seems to be working now though. Perhaps it was a connection error.

[gistub]

I am getting error: toolchain 'nightly' is not installed on two different platforms (OSX, Linux) after I do a curl https://sh.rustup.rs -sSf | sh
Machines are on different networks, so I am guessing connection problem is from rustup.rs server?

Even customizing options and selecting stable produces the same error with nightly message!

[haudan]

I'm experiencing the same problem as @gistub on my Mac. Here's a screenshot:

The tmp.4jb0Iul4 directory doesn't exist after rustup yields the error, so no wonder the command fails.
Is this a problem or does rustup simply remove the directory after it quits?

[brson]

@Lisoph the non-existence of the files is expected (though certainly annoying for debugging). rustup should probably have a mode where it doesn't clean up temp files.

Well, this is pretty terrible bug. I'll try to look into it soon. Related to #275 and #277.

[kamalmarhubi]

I'm seeing this as well:

error: toolchain 'stable' is not installed
rustup: command failed: /tmp/tmp.jBjZbBTkrb/rustup-init

I was using multirust previously and did not delete any directories.

$ cat /etc/os-release 
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

[pauljt]

@Lisoph @gistub FWIW I had the issue both of you. I had previously had multirust and I'd following the prompts from rustup to remove metadata prior to installation but I still had the same error. For me, removing the ~/.multirust directory completely, and then re-running rustup-init fixed the problem for me.

[Hoverbear]

Great digging @pauljt