Package: dh-python
Version: 1.20131021-1~bpo70+1
Severity: normal
I do have
export PYBUILD_TEST_NOSE=1
%:
dh $@ --with python2,python3 --buildsystem=pybuild
override_dh_auto_test:
xvfb-run --auto-servernum --server-num=20 dh_auto_test $@
while backporting a perspective package to wheezy build fails
debian/rules override_dh_auto_test
make[1]: Entering directory `/tmp/buildd/seaborn-0.3.0'
xvfb-run --auto-servernum --server-num=20 dh_auto_test override_dh_auto_test
/usr/bin/python2.7: No module named nose.__main__; 'nose' is a package and
cannot be directly executed
E: pybuild pybuild:256: test: plugin distutils failed with: exit code=1: cd
'/tmp/buildd/seaborn-0.3.0/.pybuild/pythonX.Y_2.7/build'; python2.7 -m nose
--with-doctest
dh_auto_test: pybuild --test -i python{version} -p 2.7 2.6 --dir . returned
exit code 13
make[1]: *** [override_dh_auto_test] Error 13
make[1]: Leaving directory `/tmp/buildd/seaborn-0.3.0'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
I wondered what was the reason/advantage for
cd {build_dir}; {interpreter} -m nose --with-doctest
instead of
cd {build_dir}; {interpreter} /usr/bin/nosetests --with-doctest
?
should be ok since both 2 and 3 scriptsare the same beasts:
$> diff /usr/bin/nosetests /usr/bin/nosetests3
1c1
< #! /usr/bin/python
---
> #! /usr/bin/python3
cheers,
-- System Information:
Debian Release: 7.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages dh-python depends on:
ii python3 3.2.3-6
dh-python recommends no packages.
dh-python suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
