Bug#1120064: transition: octomap

Jose Luis Blanco-Claraco jlblanco at ual.es
Tue Nov 4 18:34:53 GMT 2025


Package: release.debian.org
Severity: normal
X-Debbugs-Cc: octomap at packages.debian.org, jlblanco at ual.es
Control: affects -1 + src:octomap
User: release.debian.org at packages.debian.org
Usertags: transition

I want to transition octomap from 1.9.7 to 1.10.0. 
The new version has new ABI with new SONAME (liboctomap.so.1.10, liboctomath.so.1.10, liboctovis.so.1.10).

Builds for the new version in experimental is green for all architectures. 

There are only 3 other packages depending on octomap:
Level 2:
- fcl
- mrpt
Level 3:
- dart

I chroot built them against the new octomap version with these results:
- fcl: builds OK.
- mrpt: builds OK.
- dart: 17 / 71 unit tests failed, but I'm almost totally sure that's not because of octomap...

Ben file:

title = "octomap";
is_affected = .depends ~ "liboctomap1" | .depends ~ "liboctomath1" | .depends ~ "liboctovis1";
is_good = .depends ~ "liboctomap1.10" | .depends ~ "liboctomath1.10" | .depends ~ "liboctovis1.10";
is_bad = .depends ~ "liboctomap1" | .depends ~ "liboctomath1" | .depends ~ "liboctovis1";



More information about the debian-science-maintainers mailing list