On Thu, Mar 27, 2025 at 01:20:40PM +0100, Sebastiaan Couwenberg wrote:
I've pushed a bunch more changes to fix most of the issues I encountered, that more helpful than my harsh review.Most prominent issue left is remnants of the RPATH: I: libjiplib1: file-references-package-build-path [usr/lib/x86_64-linux-gnu/libjiplib.so.1.1.5] I: python3-jiplib: file-references-package-build-path [usr/lib/python3/dist-packages/jiplib/_jiplib.cpython-313-x86_64-linux-gnu.so] Details: $ strings /tmp/libjiplib1/usr/lib/x86_64-linux-gnu/libjiplib.so.1 | grep '/build/' ${ORIGIN}:/build/jeolib-jiplib-1.1.5+ds/build $ strings /tmp/python3-jiplib/usr/lib/python3/dist-packages/jiplib/_jiplib.cpython-313-x86_64-linux-gnu.so | grep '/build/' ${ORIGIN}:/build/jeolib-jiplib-1.1.5+ds/build Caused by: SET(CMAKE_BUILD_WITH_INSTALL_RPATH TRUE) SET(CMAKE_INSTALL_RPATH "$\{ORIGIN\}:${CMAKE_CURRENT_BINARY_DIR}") SET(CMAKE_INSTALL_RPATH_USE_LINK_PATH TRUE) chrpath doesn't strip those. Using CMAKE_SKIP_RPATH might work but that causes the tests to fail because libjiplib.so.1 cannot be found despite LD_LIBRARY_PATH, not sure what's going on there. Might have to settle for a lintian override. Kind Regards,
Thanks, I managed to use pybuild and fix a few issues with the packaging in the meantime. Let me see if it assumes a better shape... -- ⢀⣴⠾⠻⢶⣦⠀ Francesco Paolo Lovergine ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ 0579 A97A 2238 EBF9 BE61 ⠈⠳⣄⠀⠀⠀⠀ ED02 0F02 A5E1 1636 86A4
