You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repository is one which failed to bloom during the migration because the python-lxml dependency is not available in Ubuntu Jammy. Since this is a python2 package it is unlikely that this dependency will be available on Ubuntu Jammy in the future and the packages relying on it may need to be patched to use an alternative.
Once this dependency issue is addressed it should be possible to release this repository in Rolling again by running bloom normally.
Packages which are not released in Rolling may not be automatically added to future stable ROS 2 distributions.
Your environment
ROS Distro: Rolling
OS Version: Ubuntu 22.04
Source or Binary build? bloom release
If binary, which release version? 2.4.0
Steps to reproduce
bloom-release -r rolling moveit
The text was updated successfully, but these errors were encountered:
We will work to resolve this as quickly as possible. One of the things blocking us is the lack of jammy/rolling docker images to be used in CI. I would much prefer to get our CI functioning again in Rolling before blooming a release. Here is the current issue in industrial_ci that is tracking the state of Jammy/Rolling in CI: ros-industrial/industrial_ci#775
@tylerjw and @henningkayser thanks for your work, would it be possible to make a rolling release available since it seems like Rolling CI is enabled and is passing?
Description
The ROS 2 Rolling Ridley distribution recently migrated to Ubuntu 22.04 Jammy using the rosdistro migration tool.
This repository is one which failed to bloom during the migration because the
python-lxml
dependency is not available in Ubuntu Jammy. Since this is a python2 package it is unlikely that this dependency will be available on Ubuntu Jammy in the future and the packages relying on it may need to be patched to use an alternative.Once this dependency issue is addressed it should be possible to release this repository in Rolling again by running bloom normally.
Packages which are not released in Rolling may not be automatically added to future stable ROS 2 distributions.
Your environment
Steps to reproduce
bloom-release -r rolling moveit
The text was updated successfully, but these errors were encountered: