Add Gazebo11/Ignition Citadel Debian Buster and Ubuntu Focal #75
Conversation
|
Can this be merged now? See ros-simulation/gazebo_ros_pkgs#1093 (comment) |
|
@tfoote what's the deployment plan for this PR. Are we going to pull these directly into the ROS / ROS 2 repos or pull them into the bootstrap repo and propagate them that way? |
|
There is discussion germane to this PR in #72 |
|
@nuclearsandwich , I'm woefully ignorant of how the sausage is made here, but from the discussion you linked, the intent of this addition should be redirected to an/the aptly-backed bootstrap repository? |
That's what I'm trying to determine. I could see us still reviewing and merging PRs here as documentation but it's not going to affect anything for the ROS build farms. |
ditto. @j-rivero what should I be doing to help move this forward? |
|
We need to manually import these into the bootstrap repository via aptly. I think @nuclearsandwich and I need to simplify that process and document how. |
|
Here's what I would propose: If this is the change that we want to make let's merge the PR here as a statement of intent if nothing else, and then I'll affect the change on the aptly-based bootstrap repo with notes that we can turn into documentation. |
|
That works for me. We should also do the same for #70 |
And for all of Ignition Citadel 😇 |
|
I needed to create the aptly mirror for focal, the buster one was already there. Update the mirrors aptly's package query format is based on reprepro's but of course keeping it the same would be too difficult. Some sed violence gets us an arg list in the right format. Snapshot and publish the ros_bootstrap repositories. Now the import jobs on the buildfarms need to run to pick these up. |
I imported the ifcfg packages when that PR was reviewed. Claire and I must have forgotten to merge this PR after discussing the issue on the rosdep key PR. |
|
@j-rivero the package list above doesn't appear to produce an installable state for gazebo11 on Focal. |
@j-rivero , since we'll need to update this to pull some Ignition dependencies, how about just pulling all Citadel at once? I think we may also need to pull DART and Ogre2. |
Are either of these libraries upstream and used by ROS packages because pulling in alternates could cause serious conflicts. |
|
|
Can gazebo use the version of libogre that ships with focal and or buster?
Keeping with system provided dependencies would be nice, |
Yes, Gazebo 11 works with Ogre 1.9. For Ogre 1.12, see ros/rosdistro#24448. Ignition Citadel also works with Ogre 1.9, but in addition to that it supports Ogre 2.1. Since Ignition Rendering is plugin based, users can use the Ogre 1 plugin, the Ogre 2 plugin, or develop their own plugin. We've been releasing debs for both Ogre plugins, using this fork for version 2, which has changes that make it possible to install Ogre 1 and 2 side-by-side: http://packages.osrfoundation.org/gazebo/ubuntu-stable/pool/main/i/ignition-rendering3/ Even though we support the Ogre 1 plugin, the Ogre 2 integration is superior in rendering quality so that's the recommend engine. |
I'm a bit lost, that fork looks +2 years old, but 19 days ago v1.12.6 was recently released:
Would any of this affect rviz's vendoring of ogre? |
Oh, they made a new repo. Both repos seem quite active. |
Ugh. Manually created it was not a good idea. I've wrote some bash lines to get the whole dependency string: gazebo-tooling/gazebodistro#4
Sounds like the best path. I don't expect problems with Ogre2, packaging modifies path and should not conflict with anything present in Debian/Ubuntu platforms supported by ROS Noetic/Foxy as far as I can say. Packages for Debian Stretch and Ubuntu Focal are available in our repository. For DART our Ubuntu Focal binaries are being built against Ubuntu's 6.9.2, so we should be safe here. For Debian Stretch I've generated the same version 6.9.2 for it, it is in our repositories.. Let me prepare the whole list for Citadel in the next minutes with the aptly syntax. |
Ignition Citadel whole suite list: Mostly the whole list of ignition-* packages + sdformat9 packages + ogre2.1. @nuclearsandwich any problem let me know please. |
j-rivero
changed the title
I'm going to go ahead and try this but can you open a new PR with the full list here. I haven't talked it over with @tfoote yet but I think we're going to convert these config files to a structure a bit more native to aptly and then start building automation around that.... you know, eventually. |
|
I didn't check all of citadel, but here's a (slooooooow) bash snippet to get $ for pkg in $(apt depends --quiet --recurse --important libignition-common3-dev 2>/dev/null | grep --invert-match -e "^[< ]") ; do if apt policy $pkg 2>/dev/null | grep --silent osrfoundation ; then echo "$pkg" ; fi ; done
libignition-common3-dev
libignition-common3-core-dev
libignition-common3-av-dev
libignition-common3-events-dev
libignition-common3-graphics-dev
libignition-common3-profiler-dev
libignition-common3
libignition-common3-av
libignition-math6-dev
libignition-common3-events
libignition-common3-graphics
libignition-common3-profiler
libignition-math6 |
|
@j-rivero and I are hammering out some technical issues with the latest import offline but as a side note, I notice that the |
Looks like Using The only things I don't see in @j-rivero's list are |
|
Unable to install libgazebo11-dev on Debian buster |
|
@nuclearsandwich @j-rivero I'm not sure why libgazebo11-dev is uninstallable. It seems like it might be because Buster is missing edit: basing that on gazebo11 itself is installable on Buster. |
For both, Noetic (ROS1) and Foxy (ROS2) we need to import gazebo11 packages together with all its dependencies. I added two files here to import all the needed files from packages.osrfoundation.org.
Some packages are affected by gazebo-tooling/release-tools#186 and don't have -dbg packages. I think this should not stop us from starting the upload in order to unblock the
gazebo_ros_pkgsporting, testing and release./cc @chapulina