# Version \* does not match other versions

**URL:** <https://discourse.julialang.org/t/version-does-not-match-other-versions/53995>\
**Category:** General Usage\
**Tags:** versioning\
**Created:** [January 26, 2021, 4:37pm UTC](https://discourse.julialang.org/t/version-does-not-match-other-versions/53995 "2021-01-26T16:37:42Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![bluesmoon](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bluesmoon/32/327_2.png) [@bluesmoon](https://discourse.julialang.org/u/bluesmoon)\
**Post date:** [January 26, 2021, 4:37pm UTC](https://discourse.julialang.org/t/version-does-not-match-other-versions/53995/1 "2021-01-26T16:37:43Z")

</div>

I’m using Julia 1.5.3

Trying to run my tests locally, and I get this error about `PyCall` version conflicts.  
My own package has a PyCall version dependency of `*` whereas some other package (not one of mine) has a PyCall version dependency of `1.18.0-1.18.5, 1.90.0, 1.91.0-1.91.4, 1.92.0-1.92.1`

Any idea how I could get around this issue?

```julia
Pkg.Resolve.ResolverError("Unsatisfiable requirements detected for package PyCall [438e738f]:
 PyCall [438e738f] log:
  possible versions are: [1.18.0-1.18.5, 1.90.0, 1.91.0-1.91.4, 1.92.0-1.92.1] or uninstalled
  restricted to versions * by Snowflake [0bb4fc32], leaving only versions [1.18.0-1.18.5, 1.90.0, 1.91.0-1.91.4, 1.92.0-1.92.1]
  Snowflake [0bb4fc32] log:
      possible versions are: 0.1.0 or uninstalled
       Snowflake [0bb4fc32] is fixed to version 0.1.0
   restricted to versions 1.92.2 by an explicit requirement — no versions left", nothing)

```

---

<div class="post-metadata">

**Author:** ![Henrique\_Becker](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/henrique_becker/32/15443_2.png) [@Henrique\_Becker](https://discourse.julialang.org/u/Henrique_Becker)\
**Post date:** [January 26, 2021, 6:02pm UTC](https://discourse.julialang.org/t/version-does-not-match-other-versions/53995/2 "2021-01-26T18:02:53Z")

</div>

I may be wrong but it seems like `Snowflake` fix the version to `1.92.2` but this version is not out yet? (or your registry is not updated) Because the list of all versions available ends at `1.92.1`.

---

<div class="post-metadata">

**Author:** ![bluesmoon](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bluesmoon/32/327_2.png) [@bluesmoon](https://discourse.julialang.org/u/bluesmoon)\
**Post date:** [January 26, 2021, 7:32pm UTC](https://discourse.julialang.org/t/version-does-not-match-other-versions/53995/3 "2021-01-26T19:32:43Z")

</div>

Snowflake’s Project.toml doesn’t list a version.

The Manifest.toml (which is automatically generated) pulled the latest version of whatever is in the registry, which is 1.92.2. This happened after running `Pkg.update` and `Pkg.resolve`.

Is there something I can specify in Manifest.toml to say that I don’t really care about the version?

---

<div class="post-metadata">

**Author:** ![Henrique\_Becker](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/henrique_becker/32/15443_2.png) [@Henrique\_Becker](https://discourse.julialang.org/u/Henrique_Becker)\
**Post date:** [January 26, 2021, 7:37pm UTC](https://discourse.julialang.org/t/version-does-not-match-other-versions/53995/4 "2021-01-26T19:37:04Z")

</div>

Wait, the `Snowflake.jl` package is not yours and when downloaded using the registry it comes with a `Manifest.toml`? I am not sure this is regular behavior. I think packages should only have `Project.toml` files, `Manifest.toml` files in packages caused bugs in the past (I record seeing some threads on discourse about this).

---

<div class="post-metadata">

**Author:** ![bluesmoon](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bluesmoon/32/327_2.png) [@bluesmoon](https://discourse.julialang.org/u/bluesmoon)\
**Post date:** [January 26, 2021, 7:49pm UTC](https://discourse.julialang.org/t/version-does-not-match-other-versions/53995/5 "2021-01-26T19:49:42Z")

</div>

Snowflake.jl is my own package, it’s not being downloaded, but when I `Pkg.add` a dependency, the Manifest.toml gets automatically updated. That’s where PyCall 1.92.2 came from.

---

<div class="post-metadata">

**Author:** ![Henrique\_Becker](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/henrique_becker/32/15443_2.png) [@Henrique\_Becker](https://discourse.julialang.org/u/Henrique_Becker)\
**Post date:** [January 26, 2021, 7:59pm UTC](https://discourse.julialang.org/t/version-does-not-match-other-versions/53995/6 "2021-01-26T19:59:50Z")

</div>

If other package had `PyCall` restricted then it should appear in the log you posted. Are you doing this in an empty/new environment (what is the environment you `dev`/`add`ed your package)? This other package is a dependency of your, or has some reason to be in the same environment you are trying to do tests?

> [@bluesmoon](#):
>
> Is there something I can specify in Manifest.toml to say that I don’t really care about the version?

No, you can’t, because the purpose of the `Manifest.toml` is to register the exact versions used the last time the environment was instantiated. However, a Manifest.toml should always be valid, as it is generated with `add` commands and things are only added if they are valid. Can you remove the `Manifest.toml` and then do a `Pkg.activate("."); Pkg.instantiate()` in a Julia terminal inside the package folder (the one with the `Project.toml`)?

---

<div class="post-metadata">

**Author:** ![bluesmoon](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bluesmoon/32/327_2.png) [@bluesmoon](https://discourse.julialang.org/u/bluesmoon)\
**Post date:** [January 26, 2021, 8:29pm UTC](https://discourse.julialang.org/t/version-does-not-match-other-versions/53995/7 "2021-01-26T20:29:36Z")

</div>

> Are you doing this in an empty/new environment (what is the environment you `dev` / `add` ed your package)?

I am doing this in the module environment by running `Pkg.test`, the module environment contains both a Project.toml and an Manifest.toml that were automatically generated via `add` and `develop` commands.

> Can you remove the `Manifest.toml` and then do a `Pkg.activate("."); Pkg.instantiate()` in a Julia terminal inside the package folder (the one with the `Project.toml` )?

That doesn’t work directly because of the dependencies on other local packages that are added via `develop`. I went back to the packages that had no internal dependencies. When I got to the second package (the first one that includes `PyCall` in its Project.toml), I got this:

```julia
(PyDB) pkg> develop /home/ubuntu/datascienceworkbench/lib/Modules-1.0/DBITypes
Path `/home/ubuntu/datascienceworkbench/lib/Modules-1.0/DBITypes` exists and looks like the correct package. Using existing path.
  Resolving package versions...
Updating `~/datascienceworkbench/lib/Modules-1.0/PyDB/Project.toml`
  [3aaf276a] + DBITypes v0.1.0 `~/datascienceworkbench/lib/Modules-1.0/DBITypes`
  [a93c6f00] + DataFrames v0.22.4
  [438e738f] + PyCall v1.92.2

```

This pulls in `PyCall 1.92.2`, which appears to be the latest version available.

---

<div class="post-metadata">

**Author:** ![FPGro](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fpgro/32/20822_2.png) [@FPGro](https://discourse.julialang.org/u/FPGro)\
**Post date:** [January 26, 2021, 10:10pm UTC](https://discourse.julialang.org/t/version-does-not-match-other-versions/53995/8 "2021-01-26T22:10:25Z")

</div>

[1.92.2](https://github.com/JuliaRegistries/General/blob/master/P/PyCall/Versions.toml) indeed seems to be the latest version. Weird enough.

Could you provide the `Project.toml` files of both `Snowflake.jl` and the offending dependency, and also of the test environment (if exists)?

---

<div class="post-metadata">

**Author:** ![bluesmoon](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bluesmoon/32/327_2.png) [@bluesmoon](https://discourse.julialang.org/u/bluesmoon)\
**Post date:** [January 26, 2021, 10:47pm UTC](https://discourse.julialang.org/t/version-does-not-match-other-versions/53995/9 "2021-01-26T22:47:11Z")

</div>

The problem is that I have no idea what the offending dependency is, and now after having run the above commands it passes, so whatever the offending dependency was has probably been upgraded.