Juliaup - doesn't garbage collect?

I recently installed Julia v1.10.2 using juliaup. Once installed, juliaup informed me that it failed to remove Julia v1.10.1, and suggested I should run juliaup gc at a later stage.

I checked the directory in question, and found several older versions; my juliaup directory looks as follows:

  • Question: what has gone wrong? What should I do?

Also, when I check the version no. in a VSCode, I’m told:

julia> VERSION

Likewise, in VSCode, when I’m running a Jupyterlab file and click on Juliareleasechannel, I’m told I’m in v1.10.1 and not in v1.10.2.

A final question…

  • Do I have to re-install all packages for every incremental update in Julia, e.g., going from v1.10.1 to v1.10.2, etc? It seems like that – in the terminal window, I’m in Julia v1.10.2, and there it spends considerable time re-installing packages.

Weirdly enough, in the REPL, I just did add Plots, but it seems to install a lot of other packages, too…

1 Like

Weird: after I had run the package manager in the REPL of the terminal, closed and re-opened VSCode, now it shows Julia v1.10.2 in release channel, etc. Strange, because I have closed and re-opened VSCode several times after I installed Julia v1.10.2

I have a similar issue: juliaup doesn’t seem to remove old versions, and juliaup gc has no effect:

PS C:\Users\dnf> juliaup st
 Default  Channel  Version                   Update
       *  beta     1.10.2+0.x64.w64.mingw32
          release  1.10.2+0.x64.w64.mingw32

PS C:\Users\dnf> ls .\.julia\juliaup\

    Directory: C:\Users\dnf\.julia\juliaup

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----        26.02.2024     09:38                julia-1.10.0+0.x64.w64.mingw32
d-----        31.12.2023     14:27                julia-1.10.0-rc1+0.x64.w64.mingw32
d-----        07.03.2024     08:52                julia-1.10.1+0.x64.w64.mingw32
d-----        07.03.2024     08:52                julia-1.10.2+0.x64.w64.mingw32
d-----        03.12.2021     09:37                julia-1.7.0+0~x64
d-----        04.02.2022     20:35                julia-1.7.1+0~x64
d-----        03.03.2023     19:00                julia-1.9.0-beta3+0.x64.w64.mingw32
d-----        05.05.2023     08:50                julia-1.9.0-rc2+0.x64.w64.mingw32
-a----        25.01.2022     20:02              0 .juliaup-lock
-a----        08.03.2024     15:54            401 juliaup.json
-a----        05.03.2024     08:54          46339 versiondb-x86_64-pc-windows-msvc.json

This is taking up multiple GB, and I want to be rid of them.

Part of why juliaup may fail to delete an install is that a julia process is currently running. Rebooting your machine may facilitate garbage collection in case you have rogue or orphaned Julia processes around.

1 Like

I restartred my Windows laptop, and ran >juliaup gc as the first thing. No success.

Is it safe to use delete the directories manually? Or will that mess up Juliaup?

For me the juliaup gc never really worked (Windows), despite rebooting or even waiting for two releases.
I always manually delete the replaced versions and never had any problems.

But yeah, it would be nice to have it done with a command.

I’ve rebooted multiple times since 2021, but v1. 7 still hangs around.

I’m just describing the initial reason why juliaup may have failed to delete an install. I think that may explain what happened here in the end: