Dear Maintainer,
The documentation at
https://salsa.debian.org/ci-team/autopkgtest/-/blob/1d2f93dc1d3ad1e3f27e3ace9a520d47372d8a20/doc/README.package-tests.rst
states that:
> Binary packages from the source package under test are always
installed for the test architecture, as though they had been specified
as |foo:${DEB_HOST_ARCH}|.
> Other dependencies in the |Depends| field are treated like cross
build-dependencies, with the testbed architecture taking the place of
the build architecture and the architecture under test taking the place
of the host architecture:
* |Multi-Arch: foreign| packages are installed for the testbed
architecture
* All other packages are installed for the architecture under
test, unless qualified with |:native| in which case the testbed
architecture is used
But in reality all other dependencies are always installed for the
testbed architecture, even Multi-Arch: same ones.
This makes it not possible to add library dependencies that are
dlopen'ed from the tested binary, if these were not a hard Depends of
the tested binary.