Open emzeat opened 2 years ago
@emzeat The update was intentional due Conan 2.x migration. The regression was not expected, it seems like we will need a new config option to cover your case, as the only available modes are check
and install
. Meanwhile, we can use lockfiles to restrict to the previous package revision.
I'll open an issue to Conan, reporting this case. Thanks for sharing.
@emzeat please, check conan-io/conan#11715
@emzeat I am using Conan in the docker container and since yesterday I've experienced the same issue with xorg
package. Running container as root
and updating Conan to 1.50.0 is a workaround but it's a really ugly solution.
With #11698 merged the
CONAN_SYSREQUIRES_MODE
env variable is no longer honored. Instead the system always tries to run_tool.update()
which then fails when configured with check only:Is this intentional? I have a docker container which has all dependencies installed so there should really be no action required. When manually setting
tools.system.package_manager:mode=install
there is also no additional packages installed after the update so apparently the logic fails to detect that nothing needs to be installed?Thanks for any insight you might have.