Hi Paul, thanks for replying and opening the bug in the first place :).
* Paul Gevers <elb...@debian.org> [2020-11-29 22:33]:
On 29-11-2020 12:21, Debian Bug Tracking System wrote:* Drop Python dependency (Closes: #976049)I didn't dive into it, but isn't this bug a sign of the wrong libpython3*-dev package? I.e. wouldn't the better change be to (Build-)Depend on libpython3-all-dev instead of libpython3-dev?
First of, the change includes a patch to drop the Python dependency from librospack-dev in the upstream source as it is not needed in the first place.
In detail: the bug you saw: + cmake --build build Scanning dependencies of target main [ 10%] Building CXX object CMakeFiles/main.dir/main.cc.o gmake[2]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libpython3.9.so', needed by 'main'. Stop. gmake[1]: *** [CMakeFiles/Makefile2:117: CMakeFiles/main.dir/all] Error 2 gmake: *** [Makefile:160: all] Error 2 it showed up in testing (not in unstable) because librospack-dev 2.6.2-2+b1was build with libpython3-dev 3.9 but testing still has 3.8. The problem was that the build system of ros-rospack encoded libpython3.9.so into the cmake files distributed with librospack-dev so rdepends would link against it. But while librospack0d links against libpython3.9.so, librospack-dev does not use the libpython API in it's public interface so there should be no need to link against it. I tested ros-ros, the only direct downstream dependency, and it works fine and libroslib0d, the only real rdepends, does not link against libpython, either. libpython3-all-dev, as you proposed, would have worked as well but I think dropping an unneeded dependency is the better way to go.
Cheers Jochen
signature.asc
Description: PGP signature
