Differences between revisions 10 and 11
Revision 10 as of 2009-02-07 15:41:13
Size: 3501
Comment:
Revision 11 as of 2009-03-16 03:30:43
Size: 3506
Editor: anonymous
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
||<tablewidth="100%" tablestyle=""style="border: 0px hidden ;">~-[:DebianWiki/EditorGuide#translation:Translation(s)]: none-~ ||<style="border: 0px hidden ; text-align: right;"> (!) ["/Discussion"] || ||<tablewidth="100%" tablestyle=""style="border: 0px hidden ;">~-[[DebianWiki/EditorGuide#translation|Translation(s)]]: none-~ ||<style="border: 0px hidden ; text-align: right;"> (!) [[/Discussion]] ||
Line 4: Line 4:
 [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.  [[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.
Line 39: Line 39:
 * paraview [ This caused a bug [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513060 #513060], which was fixed by rebuilding paraview ]  * paraview [ This caused a bug [[http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513060|#513060]], which was fixed by rebuilding paraview ]

Translation(s): none

(!) ?/Discussion


  • 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 [Due to upload of new upstream version 4.1.3 on 2009-01-25, gromacs will be rebuild]

  • 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 [ N/A as Open MPI itself ]
  • libopenmpi-dev [ N/A as Open MPI itself ]
  • libparmetis3.1
  • libpetsc2.3.3
  • libspooles2.2
  • openmpi-bin [ N/A as Open MPI itself ]
  • paraview [ This caused a bug #513060, which was fixed by rebuilding paraview ]

  • parmetis-test
  • r-cran-rmpi [ 0.5.6-2 rebuilt against Open MPI 1.3 and uploaded on Jan 26 ]

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: //'

which will be contacted shortly, provided this approach is deemed suitable by a few of the affected maintainers we already had informal discussions with.

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