Rustup nightly install failed for the 2019-05-11 update #1849
Comments
|
Hi, Nightly can sometimes have problems like this. Could you confirm if this remains the case in a few days? If it does, then we might have something to investigate. Thanks, Daniel. |
|
Hi So i have tried it again today, same problem still presist, here's the console output: |
|
Okay, thank you @parampaa2 for trying again. So now we know there's something we need to diagnose, let's step another step along the path. Based on the log you're showing, I think you're running a slightly old copy of rustup, so let's eliminate that as a problem by first running Also, can you confirm how much free space you have on the C: partition, and whether you are running any anti-virus beyond Windows Defender? |
|
Alright, so i have recently updated the rustup using However, it still does not relieve the problem, using I recently backed up my personal data from my C: partition, which is 41 GB right now. Previously, on the first encounter of the problem, i have 33 GB. Also as an additional information, 2 (out of 36) of my friends claimed they successfully executing An addition to my current Win8.0 PC, i used VS 2015. I am running AVG antivirus, disabling it yields the same result: Thanks for your assistance, i hope these helped. |
|
Hi, Thanks for that, it has eliminated some paths of investigation, for sure. So what we're left with is a question of whether it could be a Windows-specific issue, perhaps related to path lengths, or a rustup issue with the space in your username, or something else. @rbtcollins Do you happen to have any ideas on this issue? Would it help if we had a zip of this user's |
|
The errors being logged are all during the rollback - the bk directory is for rollbacks. We're not seeing the actual error other than 'detected conflict'. Thats a ComponentConflict, which only gets emitted from dist::component::transaction::ChangedItem.dest_abs_path. add file, copy file, copy dir, move file, move dir call that. dest_abs_path stats the destination and if it exists, triggers the error. I believe the logic is this:
So this is failing at 2 because something is causing "share/doc/rust/html" to still exist in the target directory. I can think of a few possilbilities;
I'd start by looking at the rustup metadata to see if it thinks rustc-docs is installed in that toolchain presently. |
|
I should mention, I haven't looked closely at the local data store details,
so modify my suggested investigation path based on your better knowledge.
Tldr though is that we should make sure rust knows there is content at the
conflicting path before the update begins, and that it is moving it out of
the way, before suspecting platform issues.
Perhaps running with -v will help.
|
|
My working hypothesis here, since I've now seen it elsewhere, is that at least one of the manifest files in |
|
Hi @parampaa2 Could you tell me if you're still having this problem, or if you resolved it? If you're still having it, could you tell me if any of the files called If you run |
|
This is another instance of missing/corrupt manifest data. Without knowledge of the installed file, rustup cannot remove it prior to installing the updated version, and then hits a conflict due to the file already existing, and you get the error. We've got a bunch of these bugs scattered all over the place, I'm closing them all to bring order. See #2417. |
Problem
I was trying to update my
rustupto nigthly version withrustup update nightlyto the latest, which happens to be1.36.0-nightly (d595b1135 2019-05-10), but it said this instead:More in-depth console output:
Irrelevant part is cut as it repeats the same installing progress, you can see in comment history.
I am using Windows 8.0 and using CMD terminal. I tried it twice, in the VSCode terminal and directly in CMD (using administrator privilege for the latter), both yields the same result.
Steps
cargo init.rustup update nightlyPossible Solution(s)
-
Notes
Output of
rustup --version:rustup 1.17.0 (069c88ed6 2019-03-05)Output of
rustup show:I am using Windows 8.0.
This problem is encountered when following the instructions to set up the IntermezzOS in its book
Command Prompt is run both with and without administrator privilege.
The text was updated successfully, but these errors were encountered: