# Shouldn't there be a warning when package can't update to latest?

**URL:** <https://discourse.julialang.org/t/shouldnt-there-be-a-warning-when-package-cant-update-to-latest/51446>\
**Category:** Internals & Design\
**Tags:** package\
**Created:** [December 8, 2020, 9:24am UTC](https://discourse.julialang.org/t/shouldnt-there-be-a-warning-when-package-cant-update-to-latest/51446 "2020-12-08T09:24:18Z")\
**Posts on this page:** 13\
**Page:** 2

<div class="post-metadata">

**Author:** ![marius311](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/marius311/32/3953_2.png) [@marius311](https://discourse.julialang.org/u/marius311)\
**Post date:** [December 8, 2020, 11:20pm UTC](https://discourse.julialang.org/t/shouldnt-there-be-a-warning-when-package-cant-update-to-latest/51446/21 "2020-12-08T23:20:35Z")

</div>

Personally I’d find an option like this extremely useful (agree an option is the right way to go). It could look something roughly like this, to mirror what would happen if you actually did a `pkg> up`

```julia
(@v1.5) pkg> st --upgradeable
Status `~/.julia/environments/v1.5/Project.toml`
  [c52e3926] Atom v0.12.24 ⇒ v0.12.28 (latest)
  [6e4b80f9] BenchmarkTools v0.5.0 (latest)
  [052768ef] CUDA v2.0.0 ⇒ v2.1.0 (newer v2.3.0 exists)
...

```

Color would be useful too, maybe green if already at the latest version, blue if its upgradeable in this environment to the latest possible version, or yellow if a newer version exists but something is holding it back.

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [December 9, 2020, 12:32am UTC](https://discourse.julialang.org/t/shouldnt-there-be-a-warning-when-package-cant-update-to-latest/51446/22 "2020-12-09T00:32:18Z")

</div>

I think it’s informative rather than actionable. If I’m expecting to be on the current release of some dependency and that’s what I’m reading the docs for, it might take me a while to figure out why something doesn’t work because I’m actually on an older release. That said, this only matters for direct dependencies.

---

<div class="post-metadata">

**Author:** ![liuyxpp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/liuyxpp/32/9870_2.png) [@liuyxpp](https://discourse.julialang.org/u/liuyxpp)\
**Post date:** [December 9, 2020, 1:44am UTC](https://discourse.julialang.org/t/shouldnt-there-be-a-warning-when-package-cant-update-to-latest/51446/23 "2020-12-09T01:44:29Z")

</div>

Love this idea!

---

<div class="post-metadata">

**Author:** ![affans](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/affans/32/11911_2.png) [@affans](https://discourse.julialang.org/u/affans)\
**Post date:** [December 9, 2020, 2:28am UTC](https://discourse.julialang.org/t/shouldnt-there-be-a-warning-when-package-cant-update-to-latest/51446/24 "2020-12-09T02:28:26Z")

</div>

> While not recommended, I’m willing to bet that most users have at least one environment that’s their repl experimentation environment where nothing is managed. (honestly that’s probably the only environment for 80% of beginners).

It’s very rare that I use separate Project/Manifest files and use the environment infrastructure like it was supposed to be used. Most of the time I simply add a package to my global environment. It would be nice to somehow get a message saying `Package xx can not be upgraded to the latest version because of package yy.` If package `yy` is something I used for 10 minutes four months ago, I will delete it… if `yy` is a highly used package, I may then finally move to a different environment.

---

<div class="post-metadata">

**Author:** ![stillyslalom](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stillyslalom/32/45687_2.png) [@stillyslalom](https://discourse.julialang.org/u/stillyslalom)\
**Post date:** [December 9, 2020, 2:41am UTC](https://discourse.julialang.org/t/shouldnt-there-be-a-warning-when-package-cant-update-to-latest/51446/25 "2020-12-09T02:41:47Z")

</div>

Seems like this would be a boon to maintainers, too–I see a lot of issues filed that amount to “why can’t I update your package?”, which often leads to the maintainer spending time to reproduce and pin down the compatibility conflict. It’d be great to have a built-in tool to take the load off developers.

---

<div class="post-metadata">

**Author:** ![ToucheSir](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/touchesir/32/14411_2.png) [@ToucheSir](https://discourse.julialang.org/u/ToucheSir)\
**Post date:** [December 9, 2020, 2:46am UTC](https://discourse.julialang.org/t/shouldnt-there-be-a-warning-when-package-cant-update-to-latest/51446/26 "2020-12-09T02:46:00Z")

</div>

Not really adding to the discussion, but I use separate envs almost exclusively (nothing but Revise in the global env) after being burned repeatedly by package compat issues in other languages. It’s cool to see how many different workflows Pkg can accommodate.

---

<div class="post-metadata">

**Author:** ![HenriDeh](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/henrideh/32/8316_2.png) [@HenriDeh](https://discourse.julialang.org/u/HenriDeh)\
**Post date:** [December 9, 2020, 11:42am UTC](https://discourse.julialang.org/t/shouldnt-there-be-a-warning-when-package-cant-update-to-latest/51446/27 "2020-12-09T11:42:24Z")

</div>

So what do we do in order to not let this conversation being forgotten ? Shoud I open a FR in julia’s issues ?

---

<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:** [December 9, 2020, 11:58am UTC](https://discourse.julialang.org/t/shouldnt-there-be-a-warning-when-package-cant-update-to-latest/51446/28 "2020-12-09T11:58:27Z")

</div>

There’s already a similar issue about it, [https://github.com/JuliaLang/Pkg.jl/issues/1655](https://github.com/JuliaLang/Pkg.jl/issues/1655).

---

<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:** [December 9, 2020, 12:42pm UTC](https://discourse.julialang.org/t/shouldnt-there-be-a-warning-when-package-cant-update-to-latest/51446/29 "2020-12-09T12:42:37Z")

</div>

Here’s a bit of WIP towards a `--compat` flag to status: [--outdated flag to status by KristofferC · Pull Request #2284 · JuliaLang/Pkg.jl · GitHub](https://github.com/JuliaLang/Pkg.jl/pull/2284)

 ![bild](https://global.discourse-cdn.com/julialang/original/3X/1/b/1b797d401533591191a4dfc3ed6ac631779bc01d.png)

---

<div class="post-metadata">

**Author:** ![vancleve](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/vancleve/32/4183_2.png) [@vancleve](https://discourse.julialang.org/u/vancleve)\
**Post date:** [June 29, 2021, 6:02pm UTC](https://discourse.julialang.org/t/shouldnt-there-be-a-warning-when-package-cant-update-to-latest/51446/30 "2021-06-29T18:02:14Z")

</div>

that WIP looks great!

---

<div class="post-metadata">

**Author:** ![StevenSiew](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevensiew/32/218393_2.png) [@StevenSiew](https://discourse.julialang.org/u/StevenSiew)\
**Post date:** [June 29, 2021, 10:34pm UTC](https://discourse.julialang.org/t/shouldnt-there-be-a-warning-when-package-cant-update-to-latest/51446/31 "2021-06-29T22:34:13Z")

</div>

```julia
$ julia -O3
               _
   _ _ _(_)_ | Documentation: https://docs.julialang.org
  (_) | (_) (_) |
   _ _ _| |_ __ _ | Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _ | |
  | | |_| | | | (_| | | Version 1.6.1 (2021-04-23)
 _/ |\ __'_|_|_|\__'_| | Official https://julialang.org/ release
|__/ |

(@v1.6) pkg> st -c
ERROR: option 'c' is not a valid option

```

Can someone explain why this is NOT WORKING?

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [June 29, 2021, 10:37pm UTC](https://discourse.julialang.org/t/shouldnt-there-be-a-warning-when-package-cant-update-to-latest/51446/32 "2021-06-29T22:37:39Z")

</div>

Because the pull request linked in the message above has never been merged

---

<div class="post-metadata">

**Author:** ![gustaphe](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gustaphe/32/18174_2.png) [@gustaphe](https://discourse.julialang.org/u/gustaphe)\
**Post date:** [June 30, 2021, 3:59am UTC](https://discourse.julialang.org/t/shouldnt-there-be-a-warning-when-package-cant-update-to-latest/51446/33 "2021-06-30T03:59:17Z")

</div>

This post was temporarily hidden by the community for possibly being off-topic, unfocused, inappropriate, or spammy.

[Previous page](https://discourse.julialang.org/t/shouldnt-there-be-a-warning-when-package-cant-update-to-latest/51446.md?page=1)