(@v1.7) pkg> add Turing@0.18.0
Updating registry at `~/.julia/registries/General.toml`
Resolving package versions...
ERROR: Unsatisfiable requirements detected for package Libtask [6f1fad26]:
Libtask [6f1fad26] log:
├─possible versions are: 0.1.1-0.5.3 or uninstalled
├─restricted by compatibility requirements with Turing [fce5fe82] to versions: [0.4.0-0.4.2, 0.5.3]
│ └─Turing [fce5fe82] log:
│ ├─possible versions are: 0.5.0-0.18.0 or uninstalled
│ └─restricted to versions 0.18.0 by an explicit requirement, leaving only versions 0.18.0
├─restricted by compatibility requirements with AdvancedPS [576499cb] to versions: 0.5.3
│ └─AdvancedPS [576499cb] log:
│ ├─possible versions are: 0.1.0-0.2.4 or uninstalled
│ └─restricted by compatibility requirements with Turing [fce5fe82] to versions: 0.2.4
│ └─Turing [fce5fe82] log: see above
└─restricted by compatibility requirements with Libtask_jll [3ae2931a] to versions: 0.1.1-0.4.2 or uninstalled — no versions left
└─Libtask_jll [3ae2931a] log:
├─possible versions are: 0.3.0-0.5.1 or uninstalled
└─restricted by julia compatibility requirements to versions: [0.3.0-0.3.2, 0.5.0-0.5.1] or uninstalled
Seems like because I"m running Julia 1.7.0-beta3 that Libtask can’t hit 0.5.3 and hence Turing is held WAY back.
Installed Libtask#master and it updated Turing to 0.18.0 so I guess problem solved!
BUT: it still seems like it’d be good to have a Pkg command to list available versions?
You probably don’t want to set any compat for your environment but you can use PackageCompatUI to get a list of all releases and their registration dates:
(@v1.6) pkg> add PackageCompatUI
(@v1.6) pkg> activate --temp
(jl_k7HOZz) pkg> add Turing
julia> using PackageCompatUI
julia> compat_ui()
Save and quit: q, Help: ?
> julia
Turing
Move the cursor to Turing and hit return or right arrow: