Error messages at `up`

General Usage
1

since this morning, up (on Julia 0.7.0 and 1.0.0, Win 64) gives the following message on two separate Win10 PCs

 Resolving package versions...                                                                    
  Updating `C:\Users\psoderlind\.julia\environments\v0.7\Project.toml`                            
 [no changes]                                                                                     
  Updating `C:\Users\psoderlind\.julia\environments\v0.7\Manifest.toml`                           
 [no changes]                                                                                     
ERROR: MethodError: no method matching getindex(::Nothing, ::String)                              
Stacktrace:                                                                                       
 [1] #build_versions#45(::Bool, ::Function, ::Pkg.Types.Context, ::Array{Base.UUID,1}) at C:\cygwi
\home\Administrator\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v0.7\Pkg\src\Operat
ons.jl:1016                                                                                       
 [2] build_versions at C:\cygwin\home\Administrator\buildbot\worker\package_win64\build\usr\share\
ulia\stdlib\v0.7\Pkg\src\Operations.jl:1005 [inlined]                                             
 [3] up(::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}) at C:\cygwin\home\Administrator\bui
dbot\worker\package_win64\build\usr\share\julia\stdlib\v0.7\Pkg\src\Operations.jl:1209            
...

It only seems to happen when there are no updates.

2

I eventually decided to delete environments/v0.7 and environments/v1.0 - and to reinstall all packages. Seemed to work.

3

I have exactly the same error on v0.7.0 on Mac, but I really do not want to restall all these packages. Discussions at Detect Registry UUID mismatch · Issue #695 · JuliaLang/Pkg.jl · GitHub suggest that some of the installed packages changed their UUIDs. I am wondering whether there is any way to pinpoint which packages have wrong UUIDs. If we could do this, we could only remove and reinstalled those packages, which is much more convenient.

4

The only ones where it might matter if they changed uuid is if they are developed, so you tell from pkg> status which ones are tracking a path, remove those, and reinstall them.

5

@fredrikekre, I don’t have any packages under dev although I have some master branches of certain packages, e.g.,

[23992714] MAT v0.4.0+ #master (https://github.com/JuliaIO/MAT.jl.git)
[200b8544] ORCA v0.0.0 #master (https://github.com/sglyon/ORCA.jl.git)
[f0f68f2c] PlotlyJS v0.11.0+ #master (https://github.com/sglyon/PlotlyJS.jl.git)

Should I remove those and reinstall them?

6

Yea that can have the same effect as beeing deved, you can try removing and reinstalling again if you don’t need to be on the master branch.

7

Thanks a lot! It turned out that

[200b8544] ORCA v0.0.0 #master (https://github.com/sglyon/ORCA.jl.git)

was the culprit in my case. After removing this, I don’t have that getindex error anymore!