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

octomap: 1.10.0-3 in 'rolling/distribution.yaml' [bloom] #40273

Merged
merged 1 commit into from
Mar 20, 2024

Conversation

clalancette
Copy link
Contributor

Increasing version of package(s) in repository octomap to 1.10.0-3:

@github-actions github-actions bot added the rolling Issue/PR is for the ROS 2 Rolling distribution label Mar 20, 2024
@clalancette clalancette merged commit d142c56 into ros:master Mar 20, 2024
4 checks passed
@clalancette clalancette deleted the bloom-octomap-0 branch March 20, 2024 12:06
@rhaschke
Copy link
Contributor

@clalancette, this version of octomap (1.10.0) is ABI-incompatible to the system-installed version used by libfcl (1.9.7).
Linking two different versions of a lib usually results in undefined behavior. For this reason I suggest sticking with the system-installed version, i.e. map the rosdep key octomap onto liboctomap-dev. Thoughts?

@henningkayser: fyi

Note: In Humble, we faced the problem too, but the two versions of octomap were compatible (1.9.8 vs. 1.9.7).

These packages would be possibly affected:

apt-cache rdepends ros-rolling-octomap
ros-rolling-octomap
Reverse Depends:
  ros-rolling-octomap-dbgsym
  ros-rolling-octovis
  ros-rolling-octomap-rviz-plugins
  ros-rolling-octomap-ros
  ros-rolling-dynamic-edt-3d
  ros-rolling-moveit-ros-perception
  ros-rolling-moveit-ros-occupancy-map-monitor
  ros-rolling-moveit-core
  ros-rolling-hpp-fcl
  ros-rolling-geometric-shapes

@rhaschke
Copy link
Contributor

See #41622 as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rolling Issue/PR is for the ROS 2 Rolling distribution
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants