-
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
ign -> gz: gz debs for Citadel and Fortress #788
Comments
@j-rivero , I'd appreciate some feedback on gazebo-release/gz-cmake2-release#5 before I open the remaining PRs. I'm using the same approach that we did to add I changed the |
Humm lintian didn't like me using
https://build.osrfoundation.org/job/ign-cmake2-debbuilder/1656/consoleFull Reading about transitional packages, I think I'm violating some best practices. Not sure that's the way to go in this case. https://wiki.debian.org/RenamingPackages I think what I'm trying to do here is adding a package alias, but a quick search didn't give me any hints on how to do that. @j-rivero , what do you suggest we do here? Should we do the same that was done for Garden? I guess that wouldn't break anyone, so it's backwards compatible. |
I'm proposing a change in gazebo-release/gz-cmake2-release#5 (comment) that could simplify the views about this "alias" and the Section metadata. |
Testing the
That's also true for the Garden |
I think it's due to a cmake warning
https://build.osrfoundation.org/job/ign-rendering3-debbuilder/100/consoleFull#console-section-8 need to backport gazebo-release/gz-rendering6-release#7 |
Ah easy! Thanks for catching that. I'll do the backport and trigger a new release to go 🟢 |
Add
gz
wrapper packages for eachignition
one.Citadel
gz-cmake2
gz-common3
gz-fuel-tools4
gz-gui3
gz-launch2
gz-math6
gz-msgs5
gz-physics2
gz-plugin1
gz-rendering3
gz-sensors3
gz-sim3
gz-tools1
gz-transport8
gz-citadel
Fortress
gz-common4
gz-fuel-tools7
gz-gui6
gz-launch5
gz-msgs8
gz-physics5
gz-rendering6
gz-sensors6
gz-sim6
gz-transport11
gz-utils1
gz-fortress
The text was updated successfully, but these errors were encountered: