Stream: helpdesk (published)

Topic: Annoying warning message in package development

Davi Sales Barreira (Apr 10 2024 at 20:04):

I keep getting this warning:

Warning: The project dependencies or compat requirements have changed since the manifest was last resolved.
│ It is recommended to `Pkg.resolve()` or consider `Pkg.update()` if necessary.
└ @ Pkg.API ~/.julia/juliaup/julia-1.10.2+0.aarch64.apple.darwin14/share/julia/stdlib/v1.10/Pkg/src/API.jl:1807
┌ Warning: Could not use exact versions of packages in manifest, re-resolving
└ @ TestEnv ~/.julia/packages/TestEnv/shkbW/src/julia-1.9/activate_set.jl:63

No idea what is going on. I've tried running the Pkg.update and the Pkg.resolve. Still the same thing.
It shows when I run the TestEnv:

using Pkg
Pkg.activate("../../.")
using TestEnv
TestEnv.activate()

Any idea on what might be going on?

ederag (Apr 11 2024 at 07:25):

Same here, I thought it might be related to the use of

manifest = "../../Manifest.toml"

in the Project.toml. Do you have the same ?

Davi Sales Barreira (Apr 11 2024 at 12:40):

ederag said:

Same here, I thought it might be related to the use of

manifest = "../../Manifest.toml"

in the Project.toml. Do you have the same ?

No. :/

ederag (Apr 11 2024 at 16:26):

So this does not come from the manifest = , interesting.
Sorry I won't be of much help, except perhaps this: I see only

The project dependencies or compat requirements have changed since the manifest was last resolved.
It is recommended to Pkg.resolve() or consider Pkg.update() if necessary.

which was already reported: https://github.com/JuliaTesting/TestEnv.jl/issues/43

Davi Sales Barreira (Apr 11 2024 at 17:26):

Thanks, I'll check it.

Last updated: Nov 22 2024 at 04:41 UTC