Source: hdf5
Version: 1.8.4-5
Severity: important
Usertags: old-mpi-eol

Dear maintainer,

hdf5 build-depends on LAM/MPI and/or MPICH which are not developed upstream

There were several discussions on the Debian Science mailing list to EOL both
LAM/MPI and MPICH, the latest discussion happening at [1]. Please help us with
this goal by dropping the build-dependency on lam-dev and/or libmpich1.0-dev.

You currently have two possibilities to build MPI-enabled packages:

 1. You can build-depend on mpi-default-dev to build a single MPI-enabled
    package that uses Debian's default MPI implementation. The resulting
    package should use the "-mpi" suffix. This allows easy transistions to
    other MPI implementations in case it's needed. This solution is easy to
    maintain but does not allow your users to choose a different implementation
    than the default.
 2. You can build packages against all currently supported MPI implementations
    in Debian, which are Open MPI (openmpi) and MPICH2 (mpich2). You have to
    change your build scripts to build against both implementations. There is
    no automatic way to do this at the moment. The resulting packages should
    use the "-openmpi" and "-mpich2" suffixes. This solution is harder to
    maintain but supports all MPI implementation, so your users can choose.

You're free to choose which of the solutions you'd like to implement. If there
are any questions, feel free to write to the Debian Science Maintainers mailing
list [2].

Your package is special in this transition as it has reverse depends that might
break due to the changes. The following source packages are affected:

 - minc
 - octave3.0
 - octave3.2

If you file bugs against these packages, please use the BTS usertag for this
transition and keep [2] (or me) in the loop. Thanks in advance!

Best regards,


Pkg-grass-devel mailing list

Reply via email to