Sometime in the past week, workflows using action-gz-ci started failing on Ubuntu 24.04 (Noble) due to a change in behavior of pip when attempting to resolve a conflict between empy versions required by colcon (which is limited to empy <4 due to https://github.com/colcon/colcon-core/issues/602). Here's how the conflict occurs:
I'll mark this closed since we merged a workaround in #77. The better solution would be to use python virtual environments, but we can consider that separately.
Sometime in the past week, workflows using
action-gz-ci
started failing on Ubuntu 24.04 (Noble) due to a change in behavior ofpip
when attempting to resolve a conflict between empy versions required by colcon (which is limited to empy <4 due to https://github.com/colcon/colcon-core/issues/602). Here's how the conflict occurs:install_requires
in its setup.py without placing a version constraint on empy, which leads to empy 4.1 being installed.colcon-common-extensions
, which requires empy < 4, so empy 3.3.0 is installed and empy 4.1 is uninstalled.About a week ago, this is how it worked (see https://github.com/gazebosim/sdformat/actions/runs/9571038885/job/26387170112 for example)
Now however, after uninstalling empy 4.1,
pip
also tries to uninstall itself and fails (see https://github.com/gazebosim/sdformat/actions/runs/9701621981/job/26775660003)