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

**URL:** <https://discourse.julialang.org/t/version-of-a-new-package-master-has-no-known-version/30731>\
**Category:** General Usage\
**Created:** [November 5, 2019, 9:00am UTC](https://discourse.julialang.org/t/version-of-a-new-package-master-has-no-known-version/30731 "2019-11-05T09:00:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![misha\_mikhasenko](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/misha_mikhasenko/32/5060_2.png) [@misha\_mikhasenko](https://discourse.julialang.org/u/misha_mikhasenko)\
**Post date:** [November 5, 2019, 9:00am UTC](https://discourse.julialang.org/t/version-of-a-new-package-master-has-no-known-version/30731/1 "2019-11-05T09:00:39Z")

</div>

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.

```julia
(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?

---

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [November 5, 2019, 9:10am UTC](https://discourse.julialang.org/t/version-of-a-new-package-master-has-no-known-version/30731/2 "2019-11-05T09:10:21Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![misha\_mikhasenko](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/misha_mikhasenko/32/5060_2.png) [@misha\_mikhasenko](https://discourse.julialang.org/u/misha_mikhasenko)\
**Post date:** [November 5, 2019, 9:22am UTC](https://discourse.julialang.org/t/version-of-a-new-package-master-has-no-known-version/30731/3 "2019-11-05T09:22:31Z")

</div>

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

```julia
(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.