-
Notifications
You must be signed in to change notification settings - Fork 627
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
uv self update on Windows #7690
Comments
Thanks for the report! We'll investigate. |
Do you think you could provide an exact reproduction? i.e. in a Docker container? |
It is Windows so Docker is an issue.
I'll document the before and after of the directories. |
Oh sorry 😮💨 haha Just to cover all our bases, maybe set |
This test resulted in successful upgrade of uv and uvx. But it did not clean up properly. Details in the attached files. My hunch is that once the install creates the temp directory adjacent to the final directory and has the new files there it fails some time while renaming the directories and erasing the old files and the renamed original directory. Depending on when it bails you may or may not have a working system. Thanks. |
The temporary directory adjacent to the install directory is a separate bug that we've just fixed in the development branch of the updater library. (axodotdev/cargo-dist#1374) It'll be fixed in the next release. The temp dir actually contains the previous version rather than the newly-installed one. I'm looking into the issue with the |
0.4.17 - Minor annoyance at this point: |
Windows 10 - Powershell 7.4.5
Going from uv 0.4.15 to uv 0.4.16 using
uv self update
This upgrade has the following environment variables defined:
The initial install created C:\Python\uv\bin and put uv and uvx there.
I don't have the details about the exact sequence of events (I may have had install directory defined with the \bin)
but the uv code detected a superfluous \bin subdirectory and deleted it.
This upgrade deleted uv.exe and created a C:\Python\uv\bin\bin and C:\Python\uv\bin\tmpname directory.
The new executables were installed in those subdirectories but were not moved to C:\Python\uv\bin.
uv, of course, was subsequently not findable by the OS.
Manually moving the executables to the parent directory and deleting the two created
directories had everything working correctly with the new versions.
The text was updated successfully, but these errors were encountered: