Bug#977282: libroscpp-core-dev has a runtime dependency on runtime libraries without depending on these

Matthias Klose doko at debian.org
Sun Dec 13 15:08:00 GMT 2020


Package: src:ros-roscpp-core
Version: 0.7.2-4
Severity: serious
Tags: sid bullseye

libroscpp-core-dev has a runtime dependency on runtime libraries without
depending on these.  This is seen with the current boost transition.

$ cat /usr/lib/x86_64-linux-gnu/pkgconfig/cpp_common.pc
prefix=/usr

Name: cpp_common
Description: Description of cpp_common
Version: 0.7.2
Cflags: -I${prefix}/include
Libs:  -lcpp_common /usr/lib/x86_64-linux-gnu/libboost_system.so.1.74.0
/usr/lib/x86_64-linux-gnu/libboost_thread.so.1.74.0
/usr/lib/x86_64-linux-gnu/libconsole_bridge.so.0.4
Requires:

$ cat /usr/lib/x86_64-linux-gnu/pkgconfig/rostime.pc
prefix=/usr

Name: rostime
Description: Description of rostime
Version: 0.7.2
Cflags: -I${prefix}/include
Libs:  -lrostime /usr/lib/x86_64-linux-gnu/libboost_date_time.so.1.74.0
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.74.0
/usr/lib/x86_64-linux-gnu/libboost_thread.so.1.74.0
Requires: cpp_common

If that is really needed, then libroscpp-core-dev should depend on these runtime
libraries, so that transitions have a chance to identify these dependencies.

Or use pkgconfig files like everybody else:

 - -lboost_system -lboost_thread
 - -lboost_date_time -lboost_system


I'm only filing this for ros-roscpp-core and ros-pluginlib, however the whole
ros stack should be checked for similar issues.



More information about the debian-science-maintainers mailing list