Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: transition
scalapack 2.0 has been stabilised in experimental, I think it is now
ready for release in unstable. I have tested various client packages.
The API has not changed, the transition should be no more complicated
than updating any configurations with -lblacs-${mpi} to -scalapack-${mpi}
and any -L references to multiarch if needed.
I've marked the Ben file using openmpi, but it would be mpich (default
mpi) on m68k and sh4. scalapack now provides both openmpi and mpich
versions on all arches (except sh4 where openmpi does not build).
The libgfortran4 transition is currently taking place. I think the
collision is innocuous but tell me if you think it might be obstructive.
Drew.
Ben file:
title = "scalapack";
is_affected = .depends ~ "libscalapack-openmpi1" | .depends ~
"libscalapack-openmpi2.0";
is_good = .depends ~ "libscalapack-openmpi2.0";
is_bad = .depends ~ "libscalapack-openmpi1";
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
