Dev'ing a local package onto a Pumas/DeepPumas fails due to unavailable required package?

Uncategorized
1

Hi, I am writing a small hyper-param optimization package that would allow me to better and more easily use clusters/HPC with Pumas/DeepPumas. I was trying to install it into an existing project (after a few other package conflicts, which I fixed), but now I’m getting:

pkg> dev "C:\Users\D-LINKEVICIUS\BigHO.jl_main\BigHO.jl"
   Resolving package versions...
ERROR: Unsatisfiable requirements detected for package ProvenanceTracking [64b04e06]:
 ProvenanceTracking [64b04e06] log:
 ├─ProvenanceTracking [64b04e06] has no known versions!
 └─restricted to versions 0.4.1 - * by PumasUtilities [148d11e5] — no versions left
   └─PumasUtilities [148d11e5] log:
     ├─possible versions are: 0.9.0 or uninstalled
     ├─restricted to versions 0.9.0 by project [32f9db55], leaving only versions: 0.9.0
     │ └─project [32f9db55] log:
     │   ├─possible versions are: 0.0.0 or uninstalled
     │   └─project [32f9db55] is fixed to version 0.0.0
     └─PumasUtilities [148d11e5] is fixed to version 0.9.0

My package does not use ProvenanceTracking, is this due to some registry that is available only when installing Pumas/DeepPumas? Is there a way to go around this?

Many thanks!

2

Hi Dom,

Could you let us know the deps (and compat bounds) of the package you’re attempting to dev into it, sometimes the compat error messages generated by the pumas/deeppumas manifests end up being quite misleading.

Kind regards,
Michael

3

Hi Michael,

Of course, not a problem.

[deps]
DataFrames = "a93c6f00-e57d-5684-b7b6-d8193f3e46c0"
Distributed = "8ba89e20-285c-5b6f-9357-94700520ee1b"
JLD2 = "033835bb-8acc-5ee8-8aae-3f567f8a3819"
LatinHypercubeSampling = "a5e1c1ea-c99a-51d3-a14d-a9a37257b02d"
Logging = "56ddb016-857b-54e1-b83d-db4d58db5568"
Printf = "de0858da-6303-5e67-8744-51eddeeeb8d7"
ProgressMeter = "92933f4c-e287-5a05-a399-4b506db050ca"
Random = "9a3f8284-a2c9-5f02-9a11-845980a1fd5c"
StableRNGs = "860ef19b-820b-49d6-a774-d7a799459cd3"
StatsBase = "2913bbd2-ae8a-5f71-8c99-4fb6c76f3a91"
Test = "8dfed614-e22c-5e08-85e1-65c5234f0b40"

[weakdeps]
AlgebraOfGraphics = "cbdf2221-f076-402e-a563-3d30da359d67"
CairoMakie = "13f3f980-e62b-5c42-98c6-ff1f3baf88f0"

[compat]
AlgebraOfGraphics = "0.13.1"
CairoMakie = "0.15.13"
DataFrames = "1.8.2"
JLD2 = "0.6.6"
LatinHypercubeSampling = "1.2"
ProgressMeter = "1.7"
StableRNGs = "1"
StatsBase = "0.34"
julia = "1.11"
4

Hi, likely issues will be those compat bounds on those deps. Those need to match (or be broad enough) to work along side with is pinned by the DeepPumas version that you’re using.

For DeepPumas@0.9.0:

[compat]
AlgebraOfGraphics = "0.10.9"
CairoMakie = "0.13.10"
DataFrames = "1.7.0"
JLD2 = "0.5.15"
LatinHypercubeSampling = "1.2"
ProgressMeter = "1.7"
StableRNGs = "1"
StatsBase = "0.34"
julia = "1.11"

For DeepPumas@0.10.0:

[compat]
AlgebraOfGraphics = "0.12.4"
CairoMakie = "0.15.8"
DataFrames = "1.8.1"
JLD2 = "0.6.4"
LatinHypercubeSampling = "1.2"
ProgressMeter = "1.7"
StableRNGs = "1"
StatsBase = "0.34"
julia = "1.11"

I’d suggest that for the compats in a package keep them relatively broad rather than using specific patch versions unless you really need to. So JLD2 at 0.5, DataFrames at 1.7 etc. rather than being to tight, then it’s easier for the pkg resolver to fit them into the exact requirements of the DeepPumas manifest needs.

1 Like
5

Now sorted. I raised this initially because a few of the packages were throwing when there weren’t available version when dev’ing, but then I got the error above and wasn’t sure what’s going on. Relaxing the compats a bit (as well as just making them consistent with DeepPumas@0.9.0) devs it fine, thank you!