[Pkg-ofed-devel] Bug#769742: libopensm5: move libosmcomp3, libosmvendor4 to separate packages

[Andreas Beckmann]

Package: libopensm5
Version: 3.3.18-1
Severity: serious
User: debian-qa at lists.debian.org
Usertags: piuparts

libopensm5 ships three libraries with independent soversions:
/usr/lib/x86_64-linux-gnu/libopensm.so.5.2.1
/usr/lib/x86_64-linux-gnu/libosmcomp.so.3.0.8
/usr/lib/x86_64-linux-gnu/libosmvendor.so.4.0.0
/usr/lib/x86_64-linux-gnu/libopensm.so.5
/usr/lib/x86_64-linux-gnu/libosmcomp.so.3
/usr/lib/x86_64-linux-gnu/libosmvendor.so.4

This does not work, because soversion changes in the two other
libraries cannot be represented in the package versioning.
Right now we have in sid the package ibutils (and maybe more)
with an unusable binary:

# ldd /usr/bin/ibis 
        linux-vdso.so.1 (0x00007f30818f6000)
        libopensm.so.5 => /usr/lib/x86_64-linux-gnu/libopensm.so.5 (0x00007f30816dc000)
        libosmvendor.so.3 => not found
        libosmcomp.so.3 => /usr/lib/x86_64-linux-gnu/libosmcomp.so.3 (0x00007f30814cd000)
....

because libopensm5 ships libosmvendor.so.4 nowadays.
This is an unnoticed transition.

For jessie, this bug can be fixed with binNMUs for ibutils (and maybe
other affected packages). If the release team accepts this solution,
they may tag this bug jessie-ignore.

Please do not upload split packages to sid without getting a transition
slot and a GO from the release team.
But you may (and should) upload them to experimental.


This bug was discovered by adequate in a piuparts run.


Andreas