-
Notifications
You must be signed in to change notification settings - Fork 9
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
Support for releasing ros_gzharmonic unofficial packages for Humble/Iron #994
Comments
I've tested both dpkg error
I think it would be best if we declare the conflict in the package so users aren't faced with the scary error message from |
In #1003 I've included the patch def8aa1 that should appear when we generate the stable version. Doing it for the existing repository was a bit more complicated. |
Stable release out. All the documentation and CI in place. |
Motivation
Same as #895 but changing Garden by Harmonic and supporting ROS 2 Iron/Humble.
Roadmap:
https://github.com/j-rivero/ros_ign-gzharmonic-release
For ROS 2 Humblenot supported inros2
branchros2
branchFor ROS 2 Humblenot supported inros2
branchros-iron-ros-gzharmonic-*
packages are ready in prerelease.After stable release:
git remote add gzharmonic [email protected]:gazebo-release/ros_gz-gzharmonic-release.git && git push --all gzharmonic && git push --tags gzharmonic
GZ_RELEASE_TO_CONFLICT=garden ./release-tools/bloom/ros_gz/rename-ros_gz-pkgs.bash harmonic iron
./ros_gz-release.py.bash 0.246.0 https://github.com/gazebo-release/ros_gz-gzharmonic-release iron <token> -r 1
Testing:
Install the Gazebo prerelease repositoryapt-get remove ros-iron-ros-gzgarden* # conflictingapt-get update && apt-get install ros-iron-ros-gzharmonic
Known problems:
There could be conflicts withros-iron-ros-gzgarden
packages.The text was updated successfully, but these errors were encountered: