Version of a new package (["master"] has no known version)

General Usage
1

I have two packages under development,

  • the second, X3872.jl, depends on the first ThreeBodyDecay.jl.

While there is no specific requirement for the version of the first package, the Pkg system cannot resolve the dependence.

(v1.1) pkg> dev X3872
[ Info: Path `.julia\dev\X3872` exists and looks like the correct package, using existing path
 Resolving package versions...
ERROR: Unsatisfiable requirements detected for package ThreeBodyDecay [e6563dab]:
 ThreeBodyDecay [e6563dab] log:
 ├─ThreeBodyDecay [e6563dab] has no known versions!
 └─restricted to versions * by X3872 [f967d742] — no versions left
   └─X3872 [f967d742] log:
     ├─possible versions are: 0.1.0 or uninstalled
     └─X3872 [f967d742] is fixed to version 0.1.0

here I have already added the first package in the dependence of the second, the Project.toml points to the master.

I have a guess that Pkg wants the packages to have version tags, while only the master branch exists. Any ideas, suggestions?

2

For now, try adding ThreeBodyDecay first. There is some work in progress to better discover unregistered packages when you develop locally.

3 Likes
3

Thanks.
Something helped, what I did:

  • changed a version of the ThreeBodyDecay to 0.2.0
  • created a tag v0.2.0 and pushed to the origin.
  • added ThreeBodyDecay to the development
(v1.1) pkg> dev ThreeBodyDecay
[ Info: Path `.julia\dev\ThreeBodyDecay` exists and looks like the correct package, using existing path
 Resolving package versions...
  Updating `.julia\environments\v1.1\Project.toml`
  [21f57ea0] - ThreeBodyDecay v0.2.0 [`.julia\dev\ThreeBodyDecay`]
  [e6563dab] + ThreeBodyDecay v0.2.0 [`.julia\dev\ThreeBodyDecay`]
  Updating `.julia\environments\v1.1\Manifest.toml`
  [21f57ea0] - ThreeBodyDecay v0.2.0 [`.julia\dev\ThreeBodyDecay`]
  [e6563dab] + ThreeBodyDecay v0.2.0 [`.julia\dev\ThreeBodyDecay`]

then, dev X3872 worked.