Julia 1.13 - precompilation error for LibCURL since update

New to Julia
1

I just updated one of my systems to Julia 1.13, and am looking at a peculiar error when I try to load and upgrade some of my global environments.

So, my setup is using some variation of below shell script to automate some of the global environment upgrades:

for d in ~/.julia/environments/*/; do n=$(basename "$d"); julia --startup-file=no --project=@"$n" -e 'using Pkg; Pkg.status(); Pkg.update()'; done

And I’m consistently getting precompilation related errors for LibCURL_jll, LibCURL, Downloads and Pkg.

[ Info: Precompiling Pkg [44cfe95a-1eb2-52ea-b672-e2afdf69b78f] (caches not reused: 2 for different compilation options)
ERROR: LoadError: Precompiled image Base.PkgId(Base.UUID("f43a241f-c20a-4ad4-852c-f6b1247861c6"), "Downloads") not available with flags CacheFlags(; use_pkgimages=true, debug_level=1, check_bounds=0, inline=true, opt_level=2)

in expression starting at /home/.julia/juliaup/julia-1.13.0+0.x64.linux.gnu/share/julia/stdlib/v1.13/Pkg/src/PlatformEngines.jl:5
in expression starting at /home/.julia/juliaup/julia-1.13.0+0.x64.linux.gnu/share/julia/stdlib/v1.13/Pkg/src/Pkg.jl:3
in expression starting at stdin:5
  ✗ LibCURL_jll
  ✗ LibCURL
  ✗ Downloads
  ✗ Pkg
Precompiling Pkg finished.
  0 dependencies successfully precompiled in 4 seconds. 22 already precompiled.

┌ Downloads
│  ERROR: LoadError: Precompiled image Base.PkgId(Base.UUID("b27032c2-a3e7-50c8-80cd-2d36dbcbfd21"), "LibCURL") not available with flags CacheFlags(; use_pkgimages=true, debug_level=1, check_bounds=0, inline=true, opt_level=2)

And so on and so forth.

Activating some of the offending global environments manually shows above errors during startup again, though curiously I can still get into the package mode with ‘]’ and run update, which updates all the packages seemingly without issues.

Anyone have any idea what could be happening here, and how I could fix it?

Oh - just adding - I’m on Ubuntu LTS 24.04, and this behavior is seen across two separate machines just freshly updated to 1.13, across different types of environments.

2

Yup, I was getting this error too. I switched back to 1.12.7 because of this. I hope this gets fixed soon!

3

Ah, so it’s not just me having weird setup. I’m actually a bit relieved in a way.

For anyone involved with fixing the issue, I’d be more than happy to run tests or provide more in-depth info if it could help.

4

Try renaming the existing manifest to Manifest-v1.12.toml