Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: binnmu
nmu scalapack_2.0.2-7 . ANY . unstable . -m "Rebuild against mpich 3.3 release."
nmu mocassin_2.02.73-1 . ANY . unstable . -m "Rebuild against mpich 3.3
release."
nmu netpipe_3.7.2-7.4 . ANY . unstable . -m "Rebuild against mpich 3.3 release."
We have to rebuild all packages that were built against an alpha/beta/rc
of mpich 3.3 (i.e. a mpich package versioned 3.3~<something>-<rev>
instead of 3.x-<rev>) because their libmpich12 actually contains
libmpich.so.0 instead of libmpich.so.12
e.g.:
# ldd /usr/bin/mocassin
linux-vdso.so.1 (0x00007ffc19163000)
libgfortran.so.5 => /usr/lib/x86_64-linux-gnu/libgfortran.so.5
(0x00007f2c0badd000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f2c0b95a000)
libmpichfort.so.0 => not found
libmpich.so.0 => not found
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x00007f2c0b940000)
libquadmath.so.0 => /usr/lib/x86_64-linux-gnu/libquadmath.so.0
(0x00007f2c0b8ff000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f2c0b73c000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f2c0b51e000)
/lib64/ld-linux-x86-64.so.2 (0x00007f2c15486000)
Luckily there are only 12 source packages building packages dependening
on libmpich12, so I could check the age of their builds manually.
Is there some tool that can examine buildinfo files (or build logs) to
find any builds (that are still in sid (or $distro)) that were done with
a particular bad package installed?
In this case I would have wanted 'libmpich12 (<< 3.3-1)' as bad version.
Andreas
