Just a datapoint:
It builds fine under sbuild:
sbuild -A -s -d unstable mpi4py_1.3.1+hg20131106-1.dsc
The test run OK there, but maybe sbuild does less environment sanitising?
As it's sbuild that gets used on the buildds, does that mean that this
is not actually a serious bug?
Wookey
--
Source: mpi4py
Version: 1.3.1+hg20131106-1
Severity: serious
From my pbuilder build log (on amd64):
...
set -e; for v in 2.7 3.4; do \
echo I: testing using python$v; \
PYTHONPATH=`/bin/ls -d /tmp/buildd/mpi4py-1.3.1+hg20131106/build/lib.*-$v` \
/usr/bin/python$v /usr/bin/nosetests -v
2 matches
Mail list logo
