On Mon, Mar 3, 2014 at 18:24:06 +0100, Sébastien Villemot wrote: > Please schedule a binNMU for scalapack on s390x. > > The shared library of scalapack/s390x currently has unsatisfied shared library > dependencies: > > (sid_s390x-dchroot)sebastien@zelenka:~$ ldd /usr/lib/libscalapack-mpich2.so > [...] > libblacsCinit-mpich2.so.1 => not found > libblacs-mpich2.so.1 => not found > > (sid_s390x-dchroot)sebastien@zelenka:~$ ls /usr/lib/libblacs*.so.1 > /usr/lib/libblacsCinit-mpich.so.1 /usr/lib/libblacsF77init-mpich.so.1 /usr/lib/libblacs-mpich.so.1 > > > This state of affairs is due to the mpich2->mpich transition, which made > blacs-mpi change the name of its shared libraries (due to the way this package > handles the openmpi vs mpich archs). > > Also note that this scalapack issue is causing petsc to FTBFS on s390x, and is > therefore blocking the ongoing superlu transition (but don't give back petsc, > it will need new a sourceful upload to get fixed). > > nmu scalapack_1.8.0-9 . s390x . -m "rebuild against a blacs-mpi built against MPICH 3" > If that means a mere rebuild changes scalapack's SONAME, then very much NAK. SONAME changes should always go with a binary package name change. Cheers, Julien
Attachment:
signature.asc
Description: Digital signature