You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to add component miri and received the following message:
$ rustup component add miri
error: component 'miri' for target 'x86_64-unknown-linux-gnu' is unavailable for download for channel '1.69.0'
If you don't need the component, you can remove it with:
rustup component remove --toolchain 1.69.0 --target x86_64-unknown-linux-gnu miri
I.e., I tried to add the component (unsuccessfully), and the instructions tell me how to remove it.
Steps
Run rustup component add miri in a directory where x86_64-unknown-linux-gnu is the default toolchain.
Possible Solution(s)
Adjust or eliminate the irrelevant error message.
Notes
No response
Rustup version
rustup 1.26.0 (5af9b9484 2023-04-05)info: This is the version for the rustup toolchain manager, not the rustc compiler.info: The currently active `rustc` version is `rustc 1.69.0 (84c898d65 2023-04-16)`
Yes, this is clearly confusing. Probably a error type used in two different places, or perhaps a context message added inappropriately. Searching for the string should let someone find the code and start looking at it readily enough.
I.e., I tried to add the component (unsuccessfully), and the instructions tell me how to remove it.
The original error message assumes that you are updating an existing toolchain but some components are no longer available. The full error message template is as follows:
component {} is unavailable for download for channel '{}'
Sometimes not all components are available in any given nightly. 1
If you don't need the component, you can remove it with:\n\n{}
Or, if there are multiple components missing:
some components unavailable for download for channel '{toolchain}': {cs_str}\n
If you don't need the components, you can remove them with:\n\n{remove_msg}\n\n{TOOLSTATE_MSG}
I believe the aforementioned situation (where a toolchain update can be "incomplete" in terms of components) is exclusive to nightlies. Is that correct, @rbtcollins?
... or I can simply say something like "if you are updating an existing toolchain and you don't need the component(s)..."
Footnotes
This line is removed when the toolchain is not nightly. ↩
Activity
rbtcollins commentedon Aug 14, 2023
Yes, this is clearly confusing. Probably a error type used in two different places, or perhaps a context message added inappropriately. Searching for the string should let someone find the code and start looking at it readily enough.
rami3l commentedon Aug 15, 2023
@rbtcollins Claim. 1
Footnotes
Is there a place for me to claim this issue instead of simply replying with "claim"? ↩
rami3l commentedon Aug 16, 2023
The original error message assumes that you are updating an existing toolchain but some components are no longer available. The full error message template is as follows:
Or, if there are multiple components missing:
I believe the aforementioned situation (where a toolchain update can be "incomplete" in terms of components) is exclusive to nightlies. Is that correct, @rbtcollins?
... or I can simply say something like "if you are updating an existing toolchain and you don't need the component(s)..."
Footnotes
This line is removed when the toolchain is not nightly. ↩
Add test to ensure resolution of rust-lang#3418
Add test to ensure resolution of rust-lang#3418
Add test to ensure resolution of rust-lang#3418
Add test to ensure resolution of rust-lang#3418
Add test to ensure resolution of rust-lang#3418
Add test to ensure resolution of rust-lang#3418
Add test to ensure resolution of rust-lang#3418
Add test to ensure resolution of #3418
smoelius commentedon Oct 26, 2023
Thanks, @rami3l!