Verbose output for removing components on toolchain update
Maintainers usually reply within 1 day
@rami3l is already working on this.
Since Oct 2, 2026.
Assessment
This issue has not been assessed yet.
Description
Problem you are trying to solve
This is the output right now for a toolchain update:
djc-2021 main rustls $ rustup update nightly
info: syncing channel updates for nightly-aarch64-apple-darwin
info: latest update on 2026-10-02 for version 1.101.0-nightly (c36f14571 2026-10-01)
info: removing previous version of component miri
info: removing previous version of component rust-std for target wasm32-unknown-unknown
info: removing previous version of component rust-src
info: removing previous version of component rust-std for target thumbv7em-none-eabihf
info: removing previous version of component llvm-tools
info: removing previous version of component cargo
info: removing previous version of component clippy
info: removing previous version of component rust-std
info: removing previous version of component rustc
info: removing previous version of component rustfmt
info: downloading 10 components
miri installed 1.50 MiB
rust-std-wasm32-unknown-unknown installed 22.05 MiB rust-src installed 5.68 MiB
rust-std-thumbv7em-none-eabihf installed 13.38 MiB
llvm-tools installed 25.61 MiB
cargo installed 8.49 MiB
clippy installed 2.74 MiB
rust-std installed 29.24 MiB
rustc installed 49.03 MiB
rustfmt installed 1.47 MiB
nightly-aarch64-apple-darwin updated - rustc 1.101.0-nightly (c36f14571 2026-10-01) (from rustc 1.100.0-nightly (2e2b193f8 2026-09-02))
info: checking for self-update (current version: 1.29.1)
IMO the "removing previous version of" lines for each component are pretty repetitive and unnecessary.
Solution you'd like
How about we remove them?
Notes
No response
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 1.1k
- Avg merge
- 1d 4m
- Merged PRs (30d)
- 47
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rust-lang/rustup
-
enhancement O-shell
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Continuous performance tracking to avoid major regressionsPossibly taken @rami3l claimed this 11 days ago. Openmeta
rust-lang/rustup#5103 · 3 comments · 4 reactions · 1 assignee ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 65/100
rust-lang/rustup#5098 · 1 comment ·
Maintainers usually reply within 1 day
-
Simplify toolchain type hierarchyPossibly taken @rami3l claimed this 18 days ago. Openenhancement
rust-lang/rustup#5092 · 8 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Config `rust-analyzer` to use the new formatting stylePossibly taken @rami3l claimed this 24 days ago. Openenhancement
rust-lang/rustup#5069 · 3 comments · 1 reaction · 1 assignee ·
Maintainers usually reply within 1 day
All issues in rust-lang/rustup
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
zcashlabs/thus-spoke-zakura#153 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
topgrade-rs/topgrade#2395 ·
Maintainers usually reply within 1 day
-
app bug windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
editor good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
funnyboy-roks/inq#54 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day