Please backport mpich2/1.3.1-1 from natty
Bug #689217 reported by
Lucas Nussbaum
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Lucid Backports |
Won't Fix
|
Undecided
|
Unassigned | ||
maverick-backports |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
this is an easy no-change backport.
Changed in lucid-backports: | |
status: | New → Won't Fix |
To post a comment you must log in.
I've opened a task for maverick-backports so that we can ensure a smooth upgrade path from Lucid through to Natty. I've also uploaded test builds for Lucid and Maverick to my PPA (https:/ /launchpad. net/~broder/ +archive/ backports- tests); the test builds should be available shortly.
For each binary package for both Lucid and Maverick, we need confirmation that the package builds, installs, and runs (where there is something to run).
mpich2 has a few reverse dependencies: gromacs-dev and gromacs-mpich in both Lucid and Maverick, additionally yorick-mpy-mpich2 in Maverick.
For rdeps, we need confirmation that the packages in the main archive still work with the backported packages without requiring a rebuild. Please confirm that the 3 packages above work in both Lucid (where applicable) and Maverick with the backported packages.
The package also has reverse build dependencies: gromacs in both Lucid and Maverick, additionally yorick in Maverick
For r-build-deps, we need confirmation that the version of the package currently in the archive still builds against the backported package. I'll submit no-change rebuilds of gromacs and yorick to my PPA once mpich2 has finished building.
The most direct way to move this backport forward would be for you to check that the packages b/i/r and that the rdeps still work.