CI Broken on rolling from missing rosdeps

[eholum-nasa]

Just some hoopla with the noble sync and prep for resolute raccoon.

On rolling:

ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
mujoco_ros2_control_plugins: No definition of [ros2_control_cmake] for OS version [noble]
mujoco_ros2_control_demos: No definition of [xacro] for OS version [noble]
mujoco_ros2_control_tests: No definition of [xacro] for OS version [noble]
mujoco_ros2_control: No definition of [transmission_interface] for OS version [noble]

Going to disable that build but opening this to remember to bring it back...

[christophfroehlich]

rolling-testing should be fine, rolling-main needs a sync on the buildfarm

[eholum-nasa]

rolling-main needs a sync on the buildfarm

Still an issue?

https://github.com/ros-controls/mujoco_ros2_control/actions/runs/25866079536/job/76008419996?pr=194#step:5:2563

[Ts-sound]

After some investigation, I identified the root cause.

The upstream project's rosdistro Rolling repository has been updated to:

ubuntu:
  - resolute

(see: https://github.com/ros/rosdistro/blame/master/rolling/distribution.yaml)

However, the ros:rolling Docker images are still based on noble (not yet updated). Related issue: osrf/docker_images#878

As a result, rosdep cannot install packages properly due to system mismatch, leading to build failures.

Related issues:

• CI build job rolling/testing failed! ros2_control_ci#821
• [CI] No module named 'mujoco' #203
• CI Broken on rolling from missing rosdeps #178

[Ts-sound]

@christophfroehlich @eholum-nasa

[christophfroehlich]

the rosdep failures from the initial post are related to your description, but
ros-controls/ros2_control_ci#821
#203
aren't. I use handcrafted docker images, and they use resolute raccoon already.