Stream: helpdesk (published)

Topic: Pkg.update is not updating for no obvious reason


view this post on Zulip Alexander Sikorski (Jan 06 2025 at 14:13):

Running ]up I get some stale dependencies, as shown by ]st --outdated -m:
⌃ [1dea7af3] OrdinaryDiffEq v6.87.0 (<v6.90.1)
Trying to force the update with ]up --m OrdinaryDiffEq@6.90.1 does not update anything, nor report why it is not installing the required version.

Why is this? Is this a known problem? What can I do about it?

view this post on Zulip Jakob Nybo Nissen (Jan 06 2025 at 14:19):

If possible, copy your Manifest.toml file.
These kinds of issues are often reported, but hard to reproduce. Make an issue on the Pkg repository with a full reproducer, attaching your Manifest and Project.toml

view this post on Zulip Mosè Giordano (Jan 06 2025 at 16:30):

Add not up

view this post on Zulip Alexander Sikorski (Jan 06 2025 at 21:50):

actually I used up since I don't want it as explicit dependency. The manifest situation was difficult, as I had my own dev'ed mega package also in it. In the end there was a dependency compat restriction not fullfillable (one dep wanted Pkg x < 0.4, the other x>0.8).
It might be helpfull to be able to somehow allow for less strict 0.x resolvement to test for such issues.

view this post on Zulip Eric Hanson (Jan 14 2025 at 16:21):

if you end up needing particular behavior from some version, it probably does make sense to add it as a dependency and add a compat bound. Since you are depending on that behavior, and that's the way to communicate your versioning needs to Pkg, even if you don't do using PkgX in your code.


Last updated: Jan 29 2025 at 04:38 UTC