Your message dated Sat, 15 Sep 2018 06:28:00 +0000
with message-id <f6695db6-0e76-3b39-5261-dccaf787d...@thykier.net>
and subject line Re: Bug#872910: transition: scalapack
has caused the Debian Bug report #872910,
regarding transition: scalapack
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
872910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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)
--- End Message ---
--- Begin Message ---
On Sun, 10 Sep 2017 01:22:08 +0800 Drew Parsons <dpars...@debian.org> wrote:
> On Sat, 2017-09-09 at 13:20 +0200, Emilio Pozuelo Monfort wrote:
> >
> > > 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.
> >
> > Do you mean source code changes are needed in the build systems to do
> > those
> > changes? Or are rebuilds enough?
>
> The ones using -lblacs will need source changes. Some scalapack clients
> may need source changes to update to multiarch lib paths. I've been in
> touch with the Debichem maintainers to let them know the upgrade is
> coming.
>
> > >
> > libgfortran4 is in testing, so that's not a blocker indeed. Please go
> > ahead.
>
> Thanks Emilio.
>
> Drew
>
>
Closing this (long done) transition bug.
Thanks,
~Niels
--- End Message ---
