Comment 2 for bug 689217

On 13/12/10 at 10:32 -0000, Evan Broder wrote:
> 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.

The r-deps and r-b-deps won't work due to the SONAME bump. Though I
don't think that it's a problem to break reverse-dependencies since we
are talking about uploading mpich2 to -backports, not to -updates.
If users want to keep using gromacs and yorick with mpich2, they can
stay with the package in the standard archive.

Lucas