Hi, على الأربعاء 9 كانون الأول 2015 05:25، كتب Antonio Terceiro: > autopkgtest does not do anything special wrt dependencies, it will > install exactly what you told it to in debian/tests/control [...] > > I am therefore closing this bug.
The problem is not that something is not installed. The problem is that the multiarch configuration for python is not right in autopkgtest (or schroot). During the package build, dh-python renames the compiled extension to contain the multiarch triplet. For some reason, only in autopkgtest, python is not properly configured to find the extension after it has been renamed, so autopkgtest runs requiring the compiled extensions fail. So should we continue to have hacks like this to get autopkgtest to find multiarch-renamed extensions? cd /usr/lib/python2.7/dist-packages/pysam gnutype=`dpkg-architecture -qDEB_TARGET_GNU_TYPE` for so in *.${gnutype}.so ; do sudo ln -sf $so `basename $so .${gnutype}.so`.so ; done http://anonscm.debian.org/cgit/debian-med/python-pysam.git/tree/debian/tests/run-nose-tests regards Afif -- Afif Elghraoui | عفيف الغراوي http://afif.ghraoui.name