I'm interested in knowing if any of the new functionality seems to misbehave for anyone.
If you are using Illumos or arm64 macos then I'd very much appreciate an indication of whether or not things seem okay since they are new platforms for us.
Finally if you're a windows user, I'd appreciate an indication that I've not broken anything. I've tried my best to do testing on Windows when I can, but I'm not a native of that platform. I'm also unsure how to set the environment variable on Windows, so if a native user could comment with how to do it I'd appreciate that for others to use.
A basic rustup update nightly on x86_64-linux after updating to it worked, but then it self-updated again and downgraded to the stable version
Installing a channel with just minor version worked fine.
Using the new rust-toolchain format seems to try to sync the channel every time I run any command:
> rustc --version
info: syncing channel updates for 'nightly-2020-11-24-x86_64-unknown-linux-gnu'
info: latest update on 2020-11-24, rust version 1.50.0-nightly (d9a105fdd 2020-11-23)
info: component 'clippy' for target 'x86_64-unknown-linux-gnu' is up to date
info: component 'rust-std' for target 'thumbv6m-none-eabi' is up to date
info: component 'rustfmt' for target 'x86_64-unknown-linux-gnu' is up to date
rustc 1.50.0-nightly (d9a105fdd 2020-11-23)
Works fine for me on x86_64-pc-windows-msvc.
Regarding environment variables on Windows: That depends on the shell you use. I don't really use the windows shells much, but this worked for me:
cmd: set RUSTUP_UPDATE_ROOT="https://dev-static.rust-lang.org/rustup"
One thing I'd like to mention is that I get the following warning if use the new toolchain file format: warning: Force-skipping unavailable component 'rust-std-x86_64-unknown-hermit'.
We've updated the version of rustup on the staging server to close the issue reported by Nemo. I would appreciate any further testing, and we'll aim for a release later today.