Your message dated Sun, 28 Feb 2010 21:45:12 +0100 (CET)
with message-id <[email protected]>
and subject line Re: Bug#571450: meep-mpich: Please drop build-dependency on
LAM/MPI and/or MPICH
has caused the Debian Bug report #571450,
regarding meep-mpich: Please drop build-dependency on LAM/MPI and/or MPICH
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
571450: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571450
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: meep-mpich
Version: 1.1.1-5
Severity: important
User: [email protected]
Usertags: old-mpi-eol
Dear maintainer,
meep-mpich build-depends on LAM/MPI and/or MPICH which are not developed
upstream
anymore.
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].
Best regards,
Manuel
--
[1] http://lists.debian.org/debian-science/2009/11/msg00010.html
[2] [email protected]
--- End Message ---
--- Begin Message ---
Source: meep-mpich
Version: 1.1.1-5
This package explicitily contains a version of meep that is linked against
the mpich library. If this library doesn't exist anymore, this package
also has no reason to exist anymore. So users should be informed about the
EOL of mpich as soon as possible.
As there already is an openmpi-version (meep-openmpi, at least there will
be if libhdf5-openmpi is available), everyone can switch ...
Thorsten
--- End Message ---
