Package: libopenmpi-dev Version: 1.10.2-11 Followup-For: Bug #817020 Hi,
Sorry, me again! Here is still a mystery after installing libopenmpi1.10 and libopenmpi-dev (both 1.10.2-11) but it may be also related to my ignorance in package management: As my source.list is 'deb http://httpredir.debian.org/debian sid main contrib non-free', here are checksums of the 2 freshly downloaded packages: patrice@kappa2:~$ sha256sum /var/cache/apt/archives/libopenmpi* 8dcb81d76ad3e738f568149dce2b56d23323143df48aa0925761ca7511d6be2c /var/cache/apt/archives/libopenmpi1.10_1.10.2-11_amd64.deb 11012e271b9f08ca2599686921b68e473ff83ec9720562fb549409ea48470c1b /var/cache/apt/archives/libopenmpi-dev_1.10.2-11_amd64.deb patrice@kappa2:~$ md5sum /var/cache/apt/archives/libopenmpi* 034d3f948aa5f0f349f865d879de7bea /var/cache/apt/archives/libopenmpi1.10_1.10.2-11_amd64.deb 71b879a4b0e7ac81594b1457f696fbf2 /var/cache/apt/archives/libopenmpi-dev_1.10.2-11_amd64.deb Note: it would be nice to have a way to check that on Debian website like on the page here https://packages.debian.org/unstable/libopenmpi1.10 Now here is what I found in the package: patrice@kappa2:~$ dpkg-deb -c /var/cache/apt/archives/libopenmpi1.10_1.10.2-11_amd64.deb | grep liboshmem lrwxrwxrwx root/root 0 2016-03-15 17:54 ./usr/lib/liboshmem.so.8.1.0 -> openmpi/lib/liboshmem.so.8.1.0 lrwxrwxrwx root/root 0 2016-03-15 17:54 ./usr/lib/liboshmem.so.8 -> liboshmem.so.8.1.0 patrice@kappa2:~$ grep "liboshmem" /var/lib/dpkg/info/libopenmpi1.10.list /usr/lib/liboshmem.so.8.1.0 /usr/lib/liboshmem.so.8 patrice@kappa2:~$ dpkg-deb -c /var/cache/apt/archives/libopenmpi-dev_1.10.2-11_amd64.deb | grep liboshmem lrwxrwxrwx root/root 0 2016-03-15 17:54 ./usr/lib/openmpi/lib/liboshmem.so -> liboshmem.so.8.1.0 lrwxrwxrwx root/root 0 2016-03-15 17:54 ./usr/lib/liboshmem.so -> liboshmem.so.8 patrice@kappa2:~$ grep "liboshmem" /var/lib/dpkg/info/libopenmpi-dev.list /usr/lib/openmpi/lib/liboshmem.so /usr/lib/liboshmem.so Here is what I got after installation of both of them: patrice@kappa2:~$ find /usr/lib -name "*liboshmem*" /usr/lib/openmpi/lib/liboshmem.so /usr/lib/liboshmem.so 1. Why after installing libopenmpi-dev symlinks are present even if there are 'broken' and not in the case of libopenmpi1.10? 2. Why the /var/lib/dpkg/info/libopenmpi1.10.list indicates files that does not exist? For the ones that would be created in post-installation scripts? 3. How does Debian PTS show the content of a package because https://packages.debian.org/sid/amd64/libopenmpi1.10/filelist mentions the target file '/usr/lib/openmpi/lib/liboshmem.so.8.1.0' that is what finally is missing in my case ? Regards, Patrice -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-1-amd64 (SMP w/24 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libopenmpi-dev depends on: ii libc6 2.22-3 ii libhwloc-dev 1.11.2-3 ii libhwloc5 1.11.2-3 ii libibverbs-dev 1.1.8-1.1 ii libopenmpi1.10 1.10.2-11 ii openmpi-common 1.10.2-11 libopenmpi-dev recommends no packages. Versions of packages libopenmpi-dev suggests: pn opennmpi-doc <none> -- no debconf information
