rustup: error: missing key: 'url'
When running rustup update, I get the following output:
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: syncing channel updates for 'nightly-x86_64-unknown-linux-gnu'
error: missing key: 'url'
stable-x86_64-unknown-linux-gnu unchanged - rustc 1.16.0 (30cf806ef 2017-03-10)
nightly-x86_64-unknown-linux-gnu update failed - rustc 1.18.0-nightly (c58c928e6 2017-04-11)
As the targets for the channels suggest, I’m running an x86_64 Linux machine. I have rustup 1.2.0 installed.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 22
- Comments: 31 (13 by maintainers)
Commits related to this issue
- Problem: nightly + rustup is broken at the moment See https://github.com/rust-lang-nursery/rustup.rs/issues/1062 for more details Solution: switch to nightly-2017-04-11 for the time being — committed to PumpkinDB/PumpkinDB by yrashk 7 years ago
- locking rust version a fix for https://github.com/rust-lang-nursery/rustup.rs/issues/1062 — committed to chrmod/traeger by chrmod 7 years ago
- Work around https://github.com/rust-lang-nursery/rustup.rs/issues/1062 — committed to tildeio/helix by chancancode 7 years ago
- Pin travis to specific nightly Because of this https://github.com/rust-lang-nursery/rustup.rs/issues/1062#issuecomment-293930677 and future failures. — committed to rofrol/Rocket by rofrol 7 years ago
For the sake of anybody stuck without rust toolchain due to this bug, this is a workaround for the install nightly:
I’ve submitted a fix for rust-lang/rust at https://github.com/rust-lang/rust/pull/41267
Hi,
Same problem here:
Then I tried
And finally:
Alex is fixing the rustbuild side of this but testing it might take some time and might not be fixed until tomorrow PDT.
@erickt and I are looking into this and coordinating investigation in the #rust-infra IRC room
I encountered this error message but re-running about an hour later succeeded. I hadn’t updated in a while, if that matters.
First run:
Second run:
I also had this problem today. The
rustup update && rustup update nightlyfix worked for me. Would it not make sense to update the necessary part automatically?@numberoverzero I had that situation too. I believe it’s because of the “downloading self-update” step in the first run, which has applied a fix. Future runs should proceed without error, hopefully.
Got a potential fix to add rustup support for unavailable packages up in #1063.
Closing as fixed upstream
@marti1125 that is a different issue - it just means that the CDN is temporarily out of sync due to caching pecularities, it should have fixed itself within a few minutes.
As a workaround for travis, in your
.travis.yml, you can change:to this, to pin to last night’s nightly for today:
This worked for me.