Your message dated Wed, 28 Jul 2010 17:47:08 +0000
with message-id <[email protected]>
and subject line Bug#571444: fixed in mpb 1.4.2-15
has caused the Debian Bug report #571444,
regarding mpb: 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.)
--
571444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571444
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: mpb
Version: 1.4.2-14
Severity: important
User: [email protected]
Usertags: old-mpi-eol
Dear maintainer,
mpb 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: mpb
Source-Version: 1.4.2-15
We believe that the bug you reported is fixed in the latest version of
mpb, which is due to be installed in the Debian FTP archive:
mpb-doc_1.4.2-15_all.deb
to main/m/mpb/mpb-doc_1.4.2-15_all.deb
mpb-mpi_1.4.2-15_i386.deb
to main/m/mpb/mpb-mpi_1.4.2-15_i386.deb
mpb_1.4.2-15.diff.gz
to main/m/mpb/mpb_1.4.2-15.diff.gz
mpb_1.4.2-15.dsc
to main/m/mpb/mpb_1.4.2-15.dsc
mpb_1.4.2-15_i386.deb
to main/m/mpb/mpb_1.4.2-15_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thorsten Alteholz <[email protected]> (supplier of updated mpb package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Wed, 28 Jul 2010 19:00:00 +0200
Source: mpb
Binary: mpb mpb-mpi mpb-doc
Architecture: source all i386
Version: 1.4.2-15
Distribution: unstable
Urgency: low
Maintainer: Thorsten Alteholz <[email protected]>
Changed-By: Thorsten Alteholz <[email protected]>
Description:
mpb - MIT Photonic-Bands
mpb-doc - MIT Photonic-Bands documentation
mpb-mpi - MIT Photonic-Bands, parallel (mpich) version
Closes: 571444
Changes:
mpb (1.4.2-15) unstable; urgency=low
.
* debian/control: bump Standards Version to 3.9.1. (No changes needed).
* debian/control: Conflicts: replaced by Breaks: for mpb-doc
* debian/control: add dependency on mpi-default-dev (Closes: #571444)
- this is needed to always depend on a working version of MPI on any
architecture
- dependency on libmpich1.0-dev and libhdf5-seriald-dev is not needed
anymore
- remove build-conflicts on lam-dev, this is automatically handled by
mpi-default-dev now
Checksums-Sha1:
45f32936d3bdcecc5014af3bccf4b8d48fbe857c 1131 mpb_1.4.2-15.dsc
2d4052566cff6c6befd31183253a908654b534f8 686488 mpb_1.4.2.orig.tar.gz
69968684680b6a1740b41a9cce2d075049cd02dd 8475 mpb_1.4.2-15.diff.gz
ef99931ef859ee0caf708e4fd92f414a061aa02d 443422 mpb-doc_1.4.2-15_all.deb
27ddf72302d1756d1c5b2ee2ffe2733a4ebe27c5 253482 mpb_1.4.2-15_i386.deb
bacabb15bedcc696341e16f2ed1efdc5ef5db4a7 236224 mpb-mpi_1.4.2-15_i386.deb
Checksums-Sha256:
240a90a146d3712e5be837d14ef8828e3cf41d898ffa652f4458fd492700c924 1131
mpb_1.4.2-15.dsc
e44c0720a5969a879fb93e48f6098d4d87e2f99d6ef49711d822f4c2249ccd61 686488
mpb_1.4.2.orig.tar.gz
91b6e86df1b19410e1ef78dfefec57f8bd1908ab6001d87f2aabfe70d2e3b660 8475
mpb_1.4.2-15.diff.gz
e2f55be1bcd107e8d947759cff4075e611049915a143419cf64394747f955064 443422
mpb-doc_1.4.2-15_all.deb
9f43bb4150130dfe32266f40cf5aa6fd31d6598e7f2c7ddea00a9c1e7dcb657d 253482
mpb_1.4.2-15_i386.deb
e98b3064b157448be795d3c56519d7bf4e519995b0ed97c9965a30c9290eaa15 236224
mpb-mpi_1.4.2-15_i386.deb
Files:
5844c3398c152747496ca166dd2b01bc 1131 science optional mpb_1.4.2-15.dsc
e1e618b0db343a7a3fc38eabd69d008b 686488 science optional mpb_1.4.2.orig.tar.gz
7d151411ca2221fb9f2cee114ad8df64 8475 science optional mpb_1.4.2-15.diff.gz
83b3efef5aebcb04dc3bf2d9c08d23d7 443422 doc optional mpb-doc_1.4.2-15_all.deb
b945b30d268b29a759481e3661ef48d7 253482 science optional mpb_1.4.2-15_i386.deb
39ff6ab2943c7568095cc4616dacc160 236224 science optional
mpb-mpi_1.4.2-15_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkxQadIACgkQ02K2KlS5mJD7pACfYZTzFSyIz7Lhq8JSDFkMzX+K
bjAAnjjiQUYG4Inf+7CyIoZA3Nni5m4d
=AkL5
-----END PGP SIGNATURE-----
--- End Message ---
