On Thu, Dec 10, 2015 at 10:52:05PM -0800, Afif Elghraoui wrote: > 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.
ci.debian.net does not use schroot anymore, since a few weeks ago. and
autopkgtest does not do anything special to packages, it just installs
them on an otherwise regular testbed, be it a schroot chroot, an lxc
container (what ci.debian.net currently uses), and so on.
> 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
Again, there is nothing special in the autopkgtest test beds. I also
don't see other python packages that contain compiled extensions needing
to do this sort of thing.
I tried python-pysam here, and after some trial and error, I can also reproduce
the same issue outside of autopkgtest. The issue is that Python load path is
being confused by the fact that you are on root of the source package:
# pwd
/tmp/python-pysam-0.8.4+ds
# ls
AUTHORS INSTALL MANIFEST.in THANKS debian install-CGAT-tools.sh
pysam.py samtools setup.cfg tests
COPYING KNOWN_BUGS README.rst benchmark doc pysam
requirements.txt save setup.py win32
# python
Python 2.7.11 (default, Dec 9 2015, 00:29:25)
[GCC 5.3.1 20151205] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import pysam
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "pysam/__init__.py", line 1, in <module>
from pysam.libchtslib import *
ImportError: No module named libchtslib
>>>
# cd /
# python
Python 2.7.11 (default, Dec 9 2015, 00:29:25)
[GCC 5.3.1 20151205] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import pysam
>>>
#
So your problem has nothing to do autopkgtest, other than the fact that
autopkgtest always starts the tests from the root of the source package.
--
Antonio Terceiro <terce...@debian.org>
signature.asc
Description: PGP signature
