[http://www.open-mpi.org Open MPI] has released version 1.3 which we uploaded to unstable on Jan 20. Upstream recommends rebuilding of all dependent packages. This page shall serve as a scratchpad to organise this rebuild.
Open MPI 1.3 transitions
Reasoning
Open MPI 1.3 was realeased on January 19 by the upstream group, and entered Debian unstable the next day. It is not guaranteed to be binary-compatible with the 1.2.* release series. Some applications (in C) appear to run fine, others (in C++) do fall over due to a change.
Upstream recommends a rebuild. Given the relatively small number of packages using Open MPI in Debian, it would be overkill to prepare parallel releases of 1.2 and 1.3.
Suggested Approach
- Identify all affected packages, contact their maintainers.
- Two weeks later, file wishlist bugs for packages that have not been rebuilt.
- Two weeks later, prepare binNMU uploads.
Affected Packages
Running apt-cache rdepends libopenmpi1 | grep "^ " | sort | uniq yields:
- gromacs-openmpi
- illuminator-demo
- libarpack2
- libboost1.37-dbg
- libboost-mpi1.37.0
- libhdf5-openmpi-1.6.6-0
- libhypre2.0.0
- libhypre-2.4.0
- libluminate7
- libmesh0.6.2
- libmesh0.6.2-pure
- libmesh0.6.3
- libopenmpi-dbg
- libopenmpi-dev
- libparmetis3.1
- libpetsc2.3.3
- libspooles2.2
- openmpi-bin
- paraview
- parmetis-test
- r-cran-rmpi
An additional run against openmpi-bin yielded no additional packages.
Then using
( for p in `apt-cache rdepends libopenmpi1 | grep "^ " | sort | uniq`; do apt-cache show $p; done ) | grep Maintainer | sort | uniq | sed 's/^Maintainer: //'
yields these maintainers
Adam C. Powell, IV <hazelsct@debian.org>
Debian Boost Team <pkg-boost-devel@lists.alioth.debian.org>
Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
Debian OpenMPI Maintainers <pkg-openmpi-maintainers@lists.alioth.debian.org>
Debian Scientific Computing Team <pkg-scicomp-devel@lists.alioth.debian.org>
Debichem Team <debichem-devel@lists.alioth.debian.org>
Dirk Eddelbuettel <edd@debian.org>
which will be contacted shortly, provided this approach is deemed suitable by a few of the affected maintainers we already had informal discussions with.