For one project, I was sticking with Julia 0.6.4 because my functions and notebooks worked with a bunch of data we are analyzing. I recently needed to do 2-D interpolations, so I did
julia> Pkg.add("Interpolations")
and the system then prompted me to run
julia> Pkg.update()
After that, all hell broke loose. Running julia 0.6.4 in a terminal or in a notebook now results in complaints about needing the SoftGlobalScope package, and the IJulia package seems to require Julia v1.0!
Is there any way to recover my v0.6.4 environment (and safely add/update packages)?
It should certainly be possible to continue using Julia 0.6.4 for as long as you want. The package manager should not install package versions which require a newer Julia version, so in theory this should all just keep working.
Obviously, in practice, something has gone wrong, but we need more information to figure out what that is. Let’s start with your regular Julia terminal (not worrying about IJulia for now). SoftGlobalScope.jl is (a) only useful on Julia 1.0 and (b) only used by default in IJulia, so you shouldn’t be seeing errors due to that just from running Julia in a terminal. Can you post:
Exactly the output you get when you run julia in a terminal
This seems to be an issue with using the latest IJulia. You should be able to use a previous version of IJulia with a compatible Julia version such as v"0.6.4".
At some point in the past, it looks like you manually checked out the master branch of IJulia. That master branch is no longer supported on Julia 0.6, which is why IJulia is broken for you. You should be able to do: Pkg.free("IJulia") to undo that operation.
Something you can also do (if freeing doesn’t solve the problem) is go in the IJulia directory and manually checkout a particular version with git. You can go on the release page and look for dates that should work and then checkout the corresponding commit hash, e.g. git checkout bb438dc04003039a3168fff9ca1a4625f3b08e2c.
I made a backup of my v0.6 directory and when something goes wrong with it I check with commit I have in the backup and revert my pacakges to these ones, which usually fix the issue.