Differences between revisions 13 and 14
Revision 13 as of 2009-04-04 18:20:08
Size: 2294
Editor: ?ManuelPrinz
Comment: Removed intro, redundant
Revision 14 as of 2009-04-04 18:23:36
Size: 2236
Editor: ?ManuelPrinz
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
 * 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.
 1. Identify all affected packages.
1. Contact the release team and the maintainers of affected packages and request binNMUs.

Translation(s): none

(!) ?/Discussion


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

  1. Identify all affected packages.
  2. Contact the release team and the maintainers of affected packages and request binNMUs.

Affected Packages

List of source packages:

  • arpack
  • boost1.37
  • boost1.38
  • gpivtools
  • gromacs
  • hdf5
  • hypre
  • illuminator
  • libgpiv
  • libmesh
  • music
  • parmetis
  • petsc
  • rmpi
  • slepc
  • spooles

List of maintainers:

Next Steps

  1. Email sent to all affected maintainers on Jan 26
  2. This initiative has been withdrawn as the consensus view appears to be to just leave things broken as they are rather than to quickly rebuild on the new packages.


CategoryDebianDevelopment