Skip to content
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

Ignition Fortress rosdep keys for Jammy #32838

Merged
merged 3 commits into from
Apr 22, 2022
Merged

Ignition Fortress rosdep keys for Jammy #32838

merged 3 commits into from
Apr 22, 2022

Conversation

chapulina
Copy link
Contributor

Please add the following dependency to the rosdep database.

Package name:

Ignition Fortress libraries

Package Upstream Source:

All libraries are on this org: https://github.com/ignitionrobotics/

Purpose of using this:

As defined on REP-2000, Ignition Fortress will be the official Ignition version to be used with ROS Humble. This adds keys for Ubuntu Jammy.

Once the rosdep keys are available, we'll make a release of ros_ign into Rolling using Fortress. ROS packages can interface with Ignition Gazebo through ros_ign, and they can also use Ignition libraries directly.

Links to Distribution Packages

@chapulina chapulina requested a review from a team as a code owner April 21, 2022 00:15
@github-actions github-actions bot added the rosdep Issue/PR is for a rosdep key label Apr 21, 2022
Copy link
Member

@nuclearsandwich nuclearsandwich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just imported these packages from the OSRF repositories.

Copy link
Contributor

@clalancette clalancette left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I'll point out that some of these keys I can't resolve currently (on an arm64 box, which is what I've been testing recently):

$ sudo apt-cache policy ignition-fortress
N: Unable to locate package ignition-fortress
$ sudo apt-cache policy libignition-gazebo6-dev
libignition-gazebo6-dev:
  Installed: (none)
  Candidate: (none)
  Version table:
$ sudo apt-cache policy libignition-gazebo6-plugins
N: Unable to locate package libignition-gazebo6-plugins
$ sudo apt-cache policy libignition-sensors6-dev
N: Unable to locate package libignition-sensors6-dev

The rest of the keys resolve just fine. Is that expected?

Copy link
Contributor

@j-rivero j-rivero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion to add ignition-gazebo python bindings, otherwise looks good.

rosdep/python.yaml Show resolved Hide resolved
Signed-off-by: Louise Poubel <[email protected]>

Co-authored-by: Jose Luis Rivero <[email protected]>
@nuclearsandwich
Copy link
Member

So I'll point out that some of these keys I can't resolve currently (on an arm64 box, which is what I've been testing recently):

The arm64 packages likely failed to import due to version discrepancies between amd64 and arm64 packages available.

Since CI is only checking the amd64 repositories at this time I think it makes sense to get these keys up for amd64 usage, thus unblocking ros_ign on Jammy, and address the platform inconsistencies in followup.

Signed-off-by: Louise Poubel <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rosdep Issue/PR is for a rosdep key
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants