Your message dated Mon, 12 May 2014 22:00:06 +0000
with message-id <[email protected]>
and subject line Bug#744116: fixed in meep-mpich2 1.2.1-1
has caused the Debian Bug report #744116,
regarding meep-mpich2: rebuild against new libmpich version?
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.)
--
744116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744116
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: meep-mpich2
Version: 1.1.1-10
Severity: normal
Hi,
meep-mpich2 is built against libmpich2-3 in unstable. However,
libmpich2-3 comes from the mpich2 (1.4.1-4.2) source package, most of
whose binary packages have been taken over by the mpich (3.1-4) source
package, which builds libmpich12. I infer that the mpich2 source
package is due to be removed once nothing depends on its remaining
binary package any more.
libmpich doesn't seem to use versioned symbols, so it's probably not
safe to load two different versions of it into the same process; under
the usual rules I think that would mean that meep-mpich2 could only
switch to a new version if it changed its own SONAME at the same time.
However, right now, libmeep-mpich2-6 has no reverse-dependencies other
than meep-mpich2, and that depends on mpich2 which eventually ends up
depending on the new libmpich; so it may well be broken right now anyway
and I think you could safely rebuild it.
If you agree, a reupload shouldn't be necessary, and the release team
should be able to do a binNMU for you on request. But if there is a
problem, then I think you need to sort out some other strategy, because
at the moment any upload of meep-mpich2 will cause it to link against
the new libmpich.
Thanks,
--
Colin Watson [[email protected]]
--- End Message ---
--- Begin Message ---
Source: meep-mpich2
Source-Version: 1.2.1-1
We believe that the bug you reported is fixed in the latest version of
meep-mpich2, which is due to be installed in the Debian FTP archive.
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 meep-mpich2 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: Sun, 11 May 2014 11:20:00 +0200
Source: meep-mpich2
Binary: meep-mpich2 libmeep-mpich2-7 libmeep-mpich2-dev
Architecture: source amd64
Version: 1.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Alteholz <[email protected]>
Changed-By: Thorsten Alteholz <[email protected]>
Description:
libmeep-mpich2-7 - library for using parallel (OpenMPI) version of meep
libmeep-mpich2-dev - development library for using parallel (OpenMPI) version
of meep
meep-mpich2 - software package for FDTD simulation, parallel (OpenMPI) version
Closes: 744116 744463 747800
Changes:
meep-mpich2 (1.2.1-1) unstable; urgency=medium
.
* new upstream version
* soname changed to 7
* debian/rules: upstream ChangeLog is now called NEWS
* debian/control: Standards Version to 3.9.5. (No changes needed).
* debian/control: switch to dh 9
* debian/control: use guile 2.0 now (Closes: #747800)
* debian/control: remove DM-Upload-Allowed:
* debian/control: rebuild against new mpich (Closes: #744116)
* debian/rules: use debhelper
* debian/rules: use --with autoreconf (Closes: #744463)
* debian/copyright: adapt years
Checksums-Sha1:
7480f0a6f9244da11971a115fd4059307b49d11a 1475 meep-mpich2_1.2.1-1.dsc
1970c183aed60af4326bb51dea9c54e71e54b6d3 731272 meep-mpich2_1.2.1.orig.tar.gz
68f4e07c6d6c14ec4a16b9ad8107fce79f16294b 5344 meep-mpich2_1.2.1-1.debian.tar.xz
0583ec300c1edef02cffff89e7758218ff5cdc27 163962 meep-mpich2_1.2.1-1_amd64.deb
a50c0f7a8ffb3ce6556cf3ef3851975d99dd903a 242282
libmeep-mpich2-7_1.2.1-1_amd64.deb
d1fa033a117cefd39bba31fae4c5eb7ea984c98b 256782
libmeep-mpich2-dev_1.2.1-1_amd64.deb
Checksums-Sha256:
bd63ef2db7c1bb756c8dd84db34d2612766c534a61690296763cb05b7125edf3 1475
meep-mpich2_1.2.1-1.dsc
f1f0683e5688d231f7dd1863939677148fc27a6744c03510e030c85d6c518ea5 731272
meep-mpich2_1.2.1.orig.tar.gz
073749546c7a194f2241a579ae9a5e2c6df81cb80cd728b87265c998a9ae8357 5344
meep-mpich2_1.2.1-1.debian.tar.xz
3997828e7247b2881bafb74cee212a0377c82f62232d186975b24afb3d2f5d74 163962
meep-mpich2_1.2.1-1_amd64.deb
72cfb2f4299fac21d36a1eb6fb5d177b00df3fe1930c8968772ffeea5695f82e 242282
libmeep-mpich2-7_1.2.1-1_amd64.deb
4e266d33108bd42d5e2c5e5f07f459c7f613c522980e94352b10d10f2162cbe9 256782
libmeep-mpich2-dev_1.2.1-1_amd64.deb
Files:
6f21eca6421acf39975da2e335277def 163962 science optional
meep-mpich2_1.2.1-1_amd64.deb
e9787ea4bb0accae1f3aafd2ed060ca8 242282 libs optional
libmeep-mpich2-7_1.2.1-1_amd64.deb
9ee82903063063dc6a7251b4f0ff83b2 256782 libdevel optional
libmeep-mpich2-dev_1.2.1-1_amd64.deb
967bbb1e7a0b1aaf762e34e5ff1da290 1475 science optional meep-mpich2_1.2.1-1.dsc
9be2e743c3a832ae922de9d955d016c5 731272 science optional
meep-mpich2_1.2.1.orig.tar.gz
b027e3ee88354dd6262717b806202aa5 5344 science optional
meep-mpich2_1.2.1-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlNw0oIACgkQ02K2KlS5mJAubQCgh6vQrBvVqRInv0kLK/I1Jwe2
T4oAnA8Wnq1csP5i4FEgxrQ5AS4y1W6z
=g7P2
-----END PGP SIGNATURE-----
--- End Message ---
