# Understanding version compatibility message

**URL:** <https://discourse.julialang.org/t/understanding-version-compatibility-message/89627>\
**Category:** General Usage\
**Created:** [November 1, 2022, 6:44pm UTC](https://discourse.julialang.org/t/understanding-version-compatibility-message/89627 "2022-11-01T18:44:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![wsshin](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/wsshin/32/360_2.png) [@wsshin](https://discourse.julialang.org/u/wsshin)\
**Post date:** [November 1, 2022, 6:44pm UTC](https://discourse.julialang.org/t/understanding-version-compatibility-message/89627/1 "2022-11-01T18:44:15Z")

</div>

In Julia 1.8, I get the following result by `pkg> st -o`:

```julia-repl
(@v1.8) pkg> st -o MyPkg1
Status `~/.julia/environments/v1.8/Project.toml`
⌅ [1766def0] MyPkg1 v0.1.4 (<v0.2.1): MyPkg2, MyPkg3, MyPkg4

```

Does this means that `MyPkg1` is restricted to v0.1.4 because `MyPkg2`, `MyPkg3`, `MyPkg4` require so, or it means that `MyPkg1` restricted to v0.1.4 restricts the other three packages?

More generally, I am trying to understand why Julia refuses to install the up-to-date-version (v0.2.1) of `MyPkg1`. It will be nice to get a list of packages that requires the lower version of `MyPkg1`.

---

<div class="post-metadata">

**Author:** ![SteffenPL](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/steffenpl/32/206270_2.png) [@SteffenPL](https://discourse.julialang.org/u/SteffenPL)\
**Post date:** [November 1, 2022, 6:54pm UTC](https://discourse.julialang.org/t/understanding-version-compatibility-message/89627/2 "2022-11-01T18:54:57Z")

</div>

The new function is explained here: [Julia v1.8 Release Notes · The Julia Language](https://docs.julialang.org/en/v1/NEWS/#Package-Manager)  
It means that there is a new function but the listed packages prevent and update.

I guess you can call `pkg> add MyPkg1@v0.2.1` and it will explain why it cannot do it.