Dear Debian mentors, I am encountering issues with dh_shlibdeps when cross-compiling with a custom sysroot. Specifically, dh_shlibdeps fails to correctly identify some dependencies in this setup, even though I have experimented with the `admindir` argument. While some dependencies are correctly found, others are not, which makes the process unreliable.
My environment details are as follows: * I am using CMake as the build system and CPack for packaging. * I am working in a multi-architecture environment, where certain dependencies lead to conflicts (e.g., packages replacing python3:amd64 with the ARM package). *I have tested both multiarch setups and isolated root filesystems, but the issue persists in identifying dependencies with dh_shlibdeps. I would appreciate guidance on the following: * What is the correct way to use dh_shlibdeps in a cross-compilation scenario where the sysroot is not /? * If the admindir argument is relevant here, what are its intended use cases, and how should it be configured for my setup? As reference, I was also asking about this in debhelper Github repository and someone there recommended me toask in this list : https://github.com/Debian/debhelper/issues/12 Thanks for your help, Alejandro
