Hello.
The attached patch is what I tried but did not work.
The outcome may be seen here in my private fork:
https://salsa.debian.org/sanvila/esys-particle/-/pipelines
Any help will be welcome. If the proposed change may be tested in salsa first,
the better.
Thanks.
--- a/debian/rules
+++ b/debian/rules
@@ -19,7 +19,7 @@ override_dh_python3:
export OMPI_MCA_plm_rsh_agent=/bin/false #workaround to start
MPI-applications in chroot
-export LD_LIBRARY_PATH :=
$(CURDIR)/debian/esys-particle/usr/lib/${DEB_HOST_MULTIARCH}/:$(CURDIR)/debian/esys-particle/usr/lib/python3/dist-packages/esys/lsm/util/:$(CURDIR)/debian/esys-particle/usr/lib/python3/dist-packages/esys/lsm/:$(LD_LIBRARY_PATH);
+export MY_LD_LIBRARY_PATH :=
$(CURDIR)/debian/esys-particle/usr/lib/${DEB_HOST_MULTIARCH}/:$(CURDIR)/debian/esys-particle/usr/lib/python3/dist-packages/esys/lsm/util/:$(CURDIR)/debian/esys-particle/usr/lib/python3/dist-packages/esys/lsm/
export PYTHONPATH :=
$(CURDIR)/debian/esys-particle/usr/lib/python3/dist-packages/:$(PYTHONPATH);
@@ -50,3 +50,6 @@ execute_after_dh_auto_install:
execute_after_dh_installdocs:
find debian -name '*.md5' -delete
find debian -name '_form0.ps' -delete
+
+override_dh_shlibdeps:
+ dh_shlibdeps -l $(MY_LD_LIBRARY_PATH)
