Package: libopenmpi1.6 Version: 1.6.5-9.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts
Hi, during tests with piuparts I noticed some jessie->stretch upgrade problems related to openmpi. I got most of them fixed by having libstdc++6 add a Breaks: libopenmpi1.6 to ensure apt kills the old openmpi stack and does not consider keeping the jessie version installed a valid option. There is one problem remaining, code-saturne gets removed instead of being upgraded, piuparts log attached (search for "kept back", there is also apt problemresolver debug output included in the log). I suspect this is caused by libopenmpi1.6 carrying a Conflicts: libopenmpi2 which hits the current version in stretch ... but the conflict probably targets some older versions of the library instead: According to http://snapshot.debian.org/binary/libopenmpi2/ there have been some ancient versions providing libopenmpi2, too: 1.5.4-2~exp2 (source: openmpi 1.5.4-2~exp2) 1.5.4-2~exp1 (source: openmpi 1.5.4-2~exp1) 1.5.4-1 (source: openmpi 1.5.4-1) Making this conflict versioned: Conflicts: libopenmpi2 (<< 2) should solve the issue that apt does not consider libopenmpi2 2.x a valid installation candidate for stretch. Please get this fixed in the upcoming jessie point release (which is hopefully the last before stretch gets released, and therefore the last chance to get this fixed properly in jessie). Unfortunately I cannot easily test that this actually improves the situation before the package appears in jessie-pu. But I'm quite confident that it should fix the issue, and it does not carry regression potential. Andreas
code-saturne_4.3.3+repack-1.log.gz
Description: application/gzip
