-
Notifications
You must be signed in to change notification settings - Fork 893
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rustup update detected conflict manifest #1408
Comments
I am having a similar issue on macOS.
Tooling version info:
|
Stable update seemed to go fine today, still got the conflict on nightly though with the manifest file:
This is on an Arch machine with rustup installed from the regular community repo, not an AUR build. |
uninstalling nightly and reinstalling it again seemed to work |
@leshow Sorry, Uninstalling nightly still not work.
|
I'm having the same issue as @jsix and have ran the same things (and received the same output). I also tried |
@jamescostian I have resolved.
|
I got this today.
Also fixed by rustup uninstall stable && rustup update stable. |
I just ran into this issue again today. Merely uninstalling and updating toolchains didn't seem to work.
I finally got angry enough that I just deleted ~/.rustup and that dealt with the problem. It also seems like livepeer ran into this same issue just a few months ago, and other people were still reporting this problem in 2018. This issue should not have been closed merely because "uninstalling nightly and reinstalling it again seemed to work" as that's just a workaround for the bug. |
@saurik 1 Thanks for reporting! #2417 is already on our radar. However, the list of Rustup maintainers has changed for quite a few times since 2018, and I'm still slowly picking up the lost context since 2023, so please bear with us 🙇♀️ Footnotes |
rustup update usually works just fine. Willing to help to debug if anyone can point me in the right direction
The text was updated successfully, but these errors were encountered: