Your message dated Mon, 30 Mar 2015 22:20:40 +0000
with message-id <e1yci2y-0002aq...@franck.debian.org>
and subject line Bug#780629: fixed in libibverbs 1.1.8-1.1
has caused the Debian Bug report #780629,
regarding libibverbs1: please add Breaks: libopenmpi1.3
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 ow...@bugs.debian.org
immediately.)
--
780629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libibverbs1
Version: 1.1.8-1
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libopenmpi1.6 src:openmpi
Hi,
while analyzing some piuparts upgrade tests I noticed some cases where
the openmpi 1.3 -> 1.6 transition does not work out as expected. If this
happens, the scoring in apt generates a tie for the scores of
libopenmpi1.3 and libopenmpi1.6 which is resolved in favor of the
package already installed. This results in some packages not being
upgraded - which is not the intended result for a distupgrade.
To work around this, I suggest to add a Breaks: libopenmpi1.3 to any
dependency of libopenmpi1.6, e.g. libibverbs1. The dependency will
have a score slightly higher that that of the dependee, which is
sufficient to break the tie the other way around.
Since libopenmpi1.6 already has a 'Conflicts: libopenmpi1.3', there is
no wheezy -> jessie upgrade patch where the obsolete libopenmpi1.3
should survive. Adding more Breaks on libopenmpi1.3, e.g. to
libibverbs1, will only help to reach this goal.
Apt problemresolver debug output before the patch:
[...]
1 libibverbs1 [ amd64 ] < 1.1.6-1 -> 1.1.8-1 > ( libs )
[...]
-1 libhdf5-openmpi-8 [ amd64 ] < none -> 1.8.13+docs-15 > ( libs )
-1 libopenmpi1.3 [ amd64 ] < 1.4.5-1 > ( libs )
-1 libopenmpi1.6 [ amd64 ] < none -> 1.6.5-9.1 > ( libs )
-2 libhdf5-openmpi-7 [ amd64 ] < 1.8.8-9+b1 > ( libs )
[...]
Starting 2
Investigating (0) gcc-4.9-base [ amd64 ] < none -> 4.9.2-10 > ( libs )
Broken gcc-4.9-base:amd64 Breaks on gcc-4.7-base [ amd64 ] < 4.7.2-5 > ( libs
) (< 4.7.3)
Considering gcc-4.7-base:amd64 2 as a solution to gcc-4.9-base:amd64 39
Added gcc-4.7-base:amd64 to the remove list
Fixing gcc-4.9-base:amd64 via remove of gcc-4.7-base:amd64
Investigating (0) libopenmpi1.6 [ amd64 ] < none -> 1.6.5-9.1 > ( libs )
Broken libopenmpi1.6:amd64 Conflicts on libopenmpi1.3 [ amd64 ] < 1.4.5-1 > (
libs )
Considering libopenmpi1.3:amd64 -1 as a solution to libopenmpi1.6:amd64 -1
Holding Back libopenmpi1.6:amd64 rather than change libopenmpi1.3:amd64
Investigating (1) libhdf5-openmpi-8 [ amd64 ] < none -> 1.8.13+docs-15 > (
libs )
Broken libhdf5-openmpi-8:amd64 Depends on libopenmpi1.6 [ amd64 ] < none ->
1.6.5-9.1 > ( libs )
Considering libopenmpi1.6:amd64 -1 as a solution to libhdf5-openmpi-8:amd64
-1
Holding Back libhdf5-openmpi-8:amd64 rather than change libopenmpi1.6:amd64
Investigating (2) libmed1 [ amd64 ] < 3.0.3-3 -> 3.0.6-7 > ( libs )
Broken libmed1:amd64 Depends on libhdf5-openmpi-8 [ amd64 ] < none ->
1.8.13+docs-15 > ( libs ) (>= 1.8.13)
Considering libhdf5-openmpi-8:amd64 -1 as a solution to libmed1:amd64 0
Holding Back libmed1:amd64 rather than change libhdf5-openmpi-8:amd64
Try to Re-Instate (3) libmed1:amd64
Done
The following packages will be REMOVED:
gcc-4.7-base
The following NEW packages will be installed:
[...]
The following packages have been kept back:
libmed1
The following packages will be upgraded:
[...]
Apt problemresolver debug output after the patch:
[...]
1 libibverbs1 [ amd64 ] < 1.1.6-1 -> 1.1.8-2 > ( libs )
[...]
-1 libhdf5-openmpi-8 [ amd64 ] < none -> 1.8.13+docs-15 > ( libs )
-1 libopenmpi1.3 [ amd64 ] < 1.4.5-1 > ( libs )
-1 libopenmpi1.6 [ amd64 ] < none -> 1.6.5-9.1 > ( libs )
-2 libhdf5-openmpi-7 [ amd64 ] < 1.8.8-9+b1 > ( libs )
[...]
Starting 2
Investigating (0) gcc-4.9-base [ amd64 ] < none -> 4.9.2-10 > ( libs )
Broken gcc-4.9-base:amd64 Breaks on gcc-4.7-base [ amd64 ] < 4.7.2-5 > ( libs
) (< 4.7.3)
Considering gcc-4.7-base:amd64 2 as a solution to gcc-4.9-base:amd64 39
Added gcc-4.7-base:amd64 to the remove list
Fixing gcc-4.9-base:amd64 via remove of gcc-4.7-base:amd64
Investigating (0) libibverbs1 [ amd64 ] < 1.1.6-1 -> 1.1.8-2 > ( libs )
Broken libibverbs1:amd64 Breaks on libopenmpi1.3 [ amd64 ] < 1.4.5-1 > ( libs
)
Considering libopenmpi1.3:amd64 -1 as a solution to libibverbs1:amd64 1
Added libopenmpi1.3:amd64 to the remove list
Fixing libibverbs1:amd64 via remove of libopenmpi1.3:amd64
Investigating (0) libhdf5-openmpi-7 [ amd64 ] < 1.8.8-9+b1 > ( libs )
Broken libhdf5-openmpi-7:amd64 Depends on libopenmpi1.3 [ amd64 ] < 1.4.5-1 >
( libs )
Considering libopenmpi1.3:amd64 -1 as a solution to libhdf5-openmpi-7:amd64
-2
Removing libhdf5-openmpi-7:amd64 rather than change libopenmpi1.3:amd64
Done
The following packages will be REMOVED:
gcc-4.7-base libhdf5-openmpi-7 libopenmpi1.3
The following NEW packages will be installed:
[...]
The following packages will be upgraded:
[...]
Attached is the patch I used to verify my suggested fix as well as the
two full piuparts logfiles. I do *not* intend to NMU libibverbs1.
Andreas
diff -Nru libibverbs-1.1.8/debian/changelog libibverbs-1.1.8/debian/changelog
--- libibverbs-1.1.8/debian/changelog 2014-05-05 20:45:06.000000000 +0200
+++ libibverbs-1.1.8/debian/changelog 2015-03-17 02:02:30.000000000 +0100
@@ -1,3 +1,10 @@
+libibverbs (1.1.8-2) UNRELEASED; urgency=medium
+
+ * Add 'Breaks: libopenmpi1.3' to smoothen the openmpi transition on some
+ wheezy -> jessie upgrade paths. (Closes: #xxxxxx)
+
+ -- Andreas Beckmann <a...@debian.org> Tue, 17 Mar 2015 02:01:00 +0100
+
libibverbs (1.1.8-1) unstable; urgency=low
* New upstream release.
diff -Nru libibverbs-1.1.8/debian/control libibverbs-1.1.8/debian/control
--- libibverbs-1.1.8/debian/control 2014-05-05 20:45:06.000000000 +0200
+++ libibverbs-1.1.8/debian/control 2015-03-17 02:00:58.000000000 +0100
@@ -10,6 +10,7 @@
Section: libs
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, adduser
+Breaks: libopenmpi1.3
Description: Library for direct userspace use of RDMA (InfiniBand/iWARP)
libibverbs is a library that allows userspace processes to use RDMA
"verbs" as described in the InfiniBand Architecture Specification and
libmed1.fail.log.gz
Description: application/gzip
libmed1.pass.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libibverbs
Source-Version: 1.1.8-1.1
We believe that the bug you reported is fixed in the latest version of
libibverbs, 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 780...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann <gre...@debian.org> (supplier of updated libibverbs 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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 28 Mar 2015 22:49:21 +0100
Source: libibverbs
Binary: libibverbs1 libibverbs-dev libibverbs1-dbg ibverbs-utils
Architecture: source
Version: 1.1.8-1.1
Distribution: unstable
Urgency: medium
Maintainer: Roland Dreier <r...@debian.org>
Changed-By: gregor herrmann <gre...@debian.org>
Description:
ibverbs-utils - Examples for the libibverbs library
libibverbs-dev - Development files for the libibverbs library
libibverbs1 - Library for direct userspace use of RDMA (InfiniBand/iWARP)
libibverbs1-dbg - Debugging symbols for the libibverbs library
Closes: 780629
Changes:
libibverbs (1.1.8-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
.
[ Andreas Beckmann ]
* Add 'Breaks: libopenmpi1.3' to smoothen the openmpi transition on some
wheezy -> jessie upgrade paths. (Closes: #780629)
Checksums-Sha1:
0ad2b36ffa49499888c0e8f375529839e27c5162 2038 libibverbs_1.1.8-1.1.dsc
91e04e0f92aa361174eace22e7979567684317b0 4704
libibverbs_1.1.8-1.1.debian.tar.xz
Checksums-Sha256:
89fc3199fa6539c2addf253ef877ac622c8d89f0ff8ce174006923d7ca53decc 2038
libibverbs_1.1.8-1.1.dsc
2c5a898fbc01152a9fa3f4f1a1cfc2d45dfbed1c315d03057c8fda992e53b980 4704
libibverbs_1.1.8-1.1.debian.tar.xz
Files:
bfff284c268e7ef3bf3100c958ab669b 2038 libs extra libibverbs_1.1.8-1.1.dsc
337fbc3c3f0f42e6f7bfae29a70b5574 4704 libs extra
libibverbs_1.1.8-1.1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQJ8BAEBCgBmBQJVFyLfXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGlqkP/0zkppqPz2Ce6oKdgLbbUPNl
s1fhK0WCYInXNQdy94TpYgRTkDvbxWPQfMAX3hibTwnvM061oNdWC99h8UNoRbOo
FoebXfFxuKBf5CJ1ljfSWmKnPefiaAdJgxzvzVf6/KYu+tk/86ma6SqJiIwyaEJr
V3oEFWcF27O4S+1padgK8mdWAE+6vs+B36KQRgSHv36hqXBqATQBqDZnNg1QYX4K
J2INZ/lsEmH7vIoKZA3v2PTG1lbuzbKmLV+wvamjKRFlVZb+2705+Il8iAXvtm94
v2weRaQ73tkFkf6IyyXqNjCEgG5W9ujkkGXQnLD5aU1fEGx8gFijD8r8JJOCXHsR
DTsAm/csZfNqfyA+JoJ8TpyDoda0QksFCmanhL1kHiu9clMmRQ1cug5l6JnehGoz
dg9t50dFb5sYY40bwWv8epmMGNIQ215oN1Yl2AiwtMsKUdYMM626QUqPXfV3l31q
TI69Q12VM/n6JNymm9VHzz4HF/1jLwM1lGrxl5Wc3V0/vtAs2FlBIcUf3a0AO1vq
KHZFHbjlOPbBX3G4Cngj1BFtXgncaP1XNgfAFD62AnFAuiJ79Hr+tvwwDk7Kema1
NwC7LxHQtLOsNXAaN9WXd/zwrMi8LT5ZXzHTvNjynQTOfTmtJ0HPFL2HYKXhp2Rp
dF05c8/bbYAdtN88Q1nk
=p6Ou
-----END PGP SIGNATURE-----
--- End Message ---
