-
Notifications
You must be signed in to change notification settings - Fork 154
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
Regression in ROS Noetic on armv8 and armhf #173
Regression in ROS Noetic on armv8 and armhf #173
Comments
Blueprint is EOL It was backported to Citadel in gazebosim/gz-msgs#143 and released with 5.7.0:
Note that the official version used by the ROS buildfarm for Noetic is Citadel, so we default to that on that branch: https://github.com/ignitionrobotics/ros_ign/blob/noetic/ros_ign_bridge/package.xml My proposed fix is to fix the buster armhf release and the upload of focal armhf to ROS: Buster armhfIt looks like the 5.7.0 release had a test failure on https://build.osrfoundation.org/job/ign-msgs5-debbuilder/120/console
Focal armhfFor Focal armhf, the 5.7.0 release was successful: https://build.osrfoundation.org/job/ign-msgs5-debbuilder/123/ But for some reason, 5.7.0 wasn't uploaded to the ROS packages: http://packages.ros.org/ros2/ubuntu/pool/main/i/ignition-msgs5/ With this PR: |
I also can't find any arm64 binaries for melodic... Is it related? |
The latest Ignition Msgs 5.8.1 has been uploaded to packages.ros.org with ros-infrastructure/reprepro-updater#129. See:
It's only missing Buster now, which should go in with: ros-infrastructure/reprepro-updater#132 After that's merged, we can trigger new Noetic releases.
I'll defer to @j-rivero on this one, |
I believe we have all the necessary The new Noetic release should go through for all architectures: Some
Not sure what that means. Is there anything else we need to do to enable them, @sloretz ? |
@mjcarroll FYI
ros_ign_bridge
is no longer building on Ubuntu Focal armhf and Debian Buster armv8 jobs due to #137On these platforms it appears to find ign-msgs5.
Compiler error failure to find OccupancyGrid message
Here are a few options to consider
The text was updated successfully, but these errors were encountered: