Preparing for Kilted sync 2025-06-16

ROS Packaging and Release Management
,
1

There have been several new and updated packages in Kilted since it was released, and it’s time to sync those new features and fixes to the main apt and dnf repositories.

There are currently 8 regressions and 271 packages to release.

We will start holding rosdistro PRs for the sync on Friday, June 13, with a plan to do the sync on Monday, June 16.

1 Like
2

Hi there, forgive the basic question, but I’m not quite sure how to interpret these status colors for foxglove_bridge:

image
image376×164 3.7 KB

We recently fixed some test failures, so hoping that the package can be released in this sync. Are there more steps we need to take to ensure that happens? (bloom again?)

3

Thanks for asking.
The left group (Nsource) is the source package build and the right (N64) is the 64-bit Linux binary package. In this case, the N prefix represents Noble.

Within each group are the three repository stages: building, testing, and main. When a package builds successfully, it is uploaded to the building repository. If some pre-defined criteria regarding which packages have been built are met, these packages are automatically transitioned from building to testing. The last stage, main, is populated from testing when a ROS Boss triggers the “sync”, like the one I intend to do next Monday.

The colors here are:

  • green, meaning that the package is built successfully
  • blue, meaning that the package was built and is present but is an older version than the one listed in rosdistro
  • red, meaning that there are no packages with that name in the repository.

I would say that in your case, your package was added to Kilted prior to initial release but was not building successfully at that time. This is why we see the blue box for Nsource main but the red box for N64 main.

The green boxes for the testing columns mean that your package should sync to main in this sync and at that time all 6 boxes should be green.

1 Like
4

Hi there, we’re in the process of making a patch-release for ur_controllers to fix the outstanding regressions.

Also, please consider merging moveit_resources: 3.1.1-1 in 'kilted/distribution.yaml' [bloom] by rhaschke · Pull Request #46428 · ros/rosdistro · GitHub and a potentially incoming release for moveit2. Those package do have a regression, though it doesn’t show in the build farm. An exec-depend on the removed gripper_controllers package basically makes installing the apt packages fail. See Remove gripper_controllers dependency by fmauch · Pull Request #3474 · moveit/moveit2 · GitHub for details.