-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ros_ign in ROS 2 Rolling has not been released on Ubuntu Jammy #219
Comments
With Ubuntu Jammy not listed as a supported platform for Gazebo V11, I'm guessing Nav2 will have to migrate it's system simulation tests to Ignition. So having |
These need to be done first:
Let us know if you need any help while migrating Nav2 to Ignition, @ruffsl , we're happy to provide guidance. |
@chapulina just checking, it seems that the first two steps were done (ros-infrastructure/reprepro-updater#143), right? Are only the rosdep keys missing? |
ros-infrastructure/reprepro-updater#143 seems to be only partial, it has only We do have debs for all of Fortress available already, and I believe @j-rivero is planning to kick off the reprepro process in the coming days. |
I think |
|
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 ignition dependencies are not yet available in Ubuntu Jammy. Once the Jammy repositories and the rosdep database are updated 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.
The text was updated successfully, but these errors were encountered: