error: conflict detected #1723
Comments
|
The same is observed for a fresh install of 1.35.0 release on Windows:
Keeping in mind the initial bug report for an update installation on linux, my current guess is that 'access denied' is likely to be due to an attempt of renaming the files that are not closed yet. |
|
The problem was finally solved on Windows 8 by running the installer with admin privileges, as per https://stackoverflow.com/questions/52542965/rust-installation-fails-on-windows-subsystem-for-linux-could-not-rename-compone/55373522#55373522 |
|
Interesting. I don't think any of us in the wg have windows 8 so we'd need assistance to diagnose, but I wouldn't be surprised if it were related to AV or similar protections. |
|
@kinnison Well, please feel free to use me as a remote agent :) |
|
@s-n-ushakov thank you. If anyone in the wg knows the right questions to ask, it'd be @rbtcollins but I think that his time for this has been curtailed due to new job. Hopefully he'll have time to kick things off at some point soon, but please don't be surprised if it takes a while. At least you have a functional toolchain, albeit clunky, for the meantime. |
|
So first things, what @bjorn3 reported was not and error with 'could not rename component file' - that is a victim, not a cause - the cause is the last - the We should add some more output after rolling back the changes to separate rollback errors - which happened from the output of the original error. This would aid in folk filing bugs and finding duplicates etc. I suspect @bjorn3 that you've had a partially written manifest as a result of the space issue; if the problem is ongoing we should get the manifest and a recursive directory directory listing (or a zip of the .rustup) and then we can figure out the current state and perhaps what bug let us get into that state. @s-n-ushakov your issue is thus entirely separate; the bug title was a false friend :). please do file a separate ticket; getting a trace with procmon of the entire IO affecting the .rustup directory in your wslv1 homedir should let us track down the error that is occuring when you run unpriviled. |
|
I freed some space and deleted nightly, so that I could install it again. |
|
@rbtcollins I have made a new attempt of a fresh install with non-elevated user rights, and I am ready to create a separate ticket. Currently I have Process Monitor logs saved in three formats:
|
|
@rbtcollins I have filed a new bug as #1912 , please have a look. Currently refraining from attaching any of ~100M Process Monitor logs, looking forward to your further suggestions/guidelines... |
|
@s-n-ushakov thanks; lets discuss there :) |
|
@bjorn3 ok. sounds like that cleared the fault for you? |
|
@rbtcollins yes, at least for now. I think I will get it again when I run low in disk space again. I will try to reproduce it by filling my disk soon. |
|
@bjorn3 Did you ever manage to reproduce this -- I think it's related to one or more of the manifest files becoming corrupted (or zero-size) in the toolchain's |
|
I tried updating with 112MB of free space. While it doesn't say "detected conflict" anymore, the error message is still confusing: With 220MB of free disk space, it does say |
|
i just encountered this same error and i had over 200 Gb of disk space when i ran i resolved the error by running then i was able to install with |
|
Locking this to avoid further noise. #2417 is the bug tracking the main aspect of this. |
Problem
rustup updatefails witherror: could not rename component file.Steps
Notes
Output of
rustup --version:rustup 1.17.0 (069c88ed6 2019-03-05)Output of
rustup show:In the past space issues have caused update problems, but I believe I have enough free space now:
rm -r ~/.rustup/toolchains/nightly-x86_64-unknown-linux-gnufixes the problem though, so it may be a space problem anyway. It would be nice to give a message that the disk is full in that case though.The text was updated successfully, but these errors were encountered: