The buildd status page for mpi4py shows some failed builds (
https://buildd.debian.org/status/package.php?p=mpi4py).  While none of
these are new (i.e., they also failed for 1.2.2-3), I think many of these
are caused by a mismatch between the control & rules.

In particular, the package build depends on 'mpi-default-bin' (
http://packages.debian.org/sid/mpi-default-bin) which depends on
openmpi-bin for most platforms and mpich2 on others.... But debian/rules
has an explicit dependency on openmpi.  I wonder if we couldn't just say
--mpicc=/usr/bin/mpicc (i.e., unset MPI) to fix the build process on the
other platforms?

Reply via email to