bloom release for rolling and lyrical

[christian-rauch]

Can you please release the Orbbec packages via bloom for the ROS distros rolling and lyrical too?

They are currently available for humble and jazzy. Thank you for this. This makes it very convenient to use the Orbbec cameras. It would be nice to have the same convenience on Ubuntu 26.04 and the upcoming ROS 2 lyrical release too.

If you release the package to rolling, it will automatically be added to future ROS 2 distributions.

Let me know if you need help with this.

[ob-yalian]

@christian-rauch Thanks for the suggestion. We will evaluate releasing the Orbbec packages via bloom for ROS 2 Rolling and Lyrical.

[christian-rauch]

I requested to be added to your release team: ros2-gbp/ros2-gbp-github-org#1038.

[ob-yalian]

@christian-rauch Currently, we maintain releases through a standalone bloom release repository orbbec_camera_v2-release rather than a GBP-based packaging workflow. I’m currently planning to migrate the release workflow to GBP.

[christian-rauch]

I see. The "gbp" repo at https://github.com/ros2-gbp/orbbec_camera_v2-release actually looks more recent. Releasing to rolling and lyrical is a good opportunity to switch the repos.

Do you have a timeline for this? Do you need help with it?

[ob-yalian]

At the moment, we have not officially validated the package on ROS 2 Rolling or Lyrical yet. While it may work similarly to other supported ROS 2 distributions, we cannot guarantee full compatibility until proper testing is completed.

We’ll keep this issue open and update it as we make progress on Rolling/Lyrical support.

[christian-rauch]

@ob-yalian See #196 for a port to lyrical. Please review this PR.

[fastcat]

In order to get bloom to make local debs from this repo, I had to de-vendor magic-enum

[christian-rauch]

In order to get bloom to make local debs from this repo, I had to de-vendor magic-enum

I am blooming the packages using the jspricke/ros-deb-builder-action action without issues.

[fastcat]

I should clarify that bloom successfully generates the debs, but they are not installable because they contain the magic enum header that conflicts with the actual magic enum package (on which other things in my environment depend)

[christian-rauch]

I guess you are referring to this header: https://github.com/orbbec/OrbbecSDK_ROS2/blob/v2-main/orbbec_camera/include/magic_enum/magic_enum.hpp

According to the bloom log at https://build.ros2.org/view/Jbin_uN64/job/Jbin_uN64__orbbec_camera__ubuntu_noble_amd64__binary/43/consoleFull, this is already an issue with the jazzy-bloomed package:

Installing: /tmp/binarydeb/ros-jazzy-orbbec-camera-2.8.6/debian/ros-jazzy-orbbec-camera/opt/ros/jazzy/include/magic_enum/magic_enum.hpp

The correct approach to fix this is to build against the Debian package libmagicenum-dev or ros-lyrical-magic-enum, instead of de-vendoring magic_enum.

[fastcat]

The correct approach to fix this is to build against the Debian package libmagicenum-dev or ros-lyrical-magic-enum, instead of de-vendoring magic_enum.

This is what I meant by de-vendoring -- remove the vendor'd header from the repo, and add the ros magic-enum package as a dependency. I did that on my company's fork and got working packages. AFAICT, so long as the header is in the repo, it ends up in the orbbec debs, and those debs become uninstallable.