Your message dated Tue, 22 Mar 2022 22:40:35 +0100
with message-id <yjpcu9jkb7wah...@ramacher.at>
and subject line Re: Bug#1006648: transition: numerical stack: slepc petsc
hypre scotch scalapack
has caused the Debian Bug report #1006648,
regarding transition: numerical stack: slepc petsc hypre scotch 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.)
--
1006648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006648
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
We've got a pile-up of numerical libraries waiting in experimental.
I'd like to clear them out into unstable. This will also let
scalapack rebuild against mpich 4.
The transitions are:
scalapack 2.1 → 2.2
scotch 6.1 → 7.0
hypre 2.22 → 2.23
petsc 3.15 → 3.16
slepc 3.15 → 3.16
hypre is now built with proper versioned library package names, so
it won't cause the same transition jam with petsc that it made last time.
auto-transitions are already generated:
https://release.debian.org/transitions/html/auto-scalapack.html
https://release.debian.org/transitions/html/auto-scotch.html
https://release.debian.org/transitions/html/auto-hypre.html
https://release.debian.org/transitions/html/auto-petsc.html
https://release.debian.org/transitions/html/auto-slepc.html
We're waiting for mpich 4 to migrate to testing. Probably best for
that to complete before starting this transition (not sure why bagel
is failing amd64 tests, perhaps it needs to rebuild against mpich 4).
Ben file:
title = "petsc";
is_affected = .depends ~ "libpetsc-real3.15" | .depends ~ "libpetsc-real3.16";
is_good = .depends ~ "libpetsc-real3.16";
is_bad = .depends ~ "libpetsc-real3.15";
--- End Message ---
--- Begin Message ---
On 2022-03-16 20:37:07, Sebastian Ramacher wrote:
> On 2022-03-16 18:35:28, Drew Parsons wrote:
> > On 2022-03-16 09:27, Sebastian Ramacher wrote:
> > > On 2022-03-15 20:33:02 +0100, Drew Parsons wrote:
> > > > Control: block 1006648 by 1006615
> > > >
> > > > On 2022-03-05 12:29, Sebastian Ramacher wrote:
> > > > > Control: tags -1 confirmed
> > > > >
> > > > > On 2022-03-01 13:34:21 +0100, Drew Parsons wrote:
> > > > > >
> > > > > > The transitions are:
> > > > > >
> > > > > > scalapack 2.1 → 2.2
> > > > > > scotch 6.1 → 7.0
> > > > > > hypre 2.22 → 2.23
> > > > > > petsc 3.15 → 3.16
> > > > > > slepc 3.15 → 3.16
> > > >
> > > > All transition packages uploaded and built, but got some turbulence
> > > > right at
> > > > the end from the pybind11 clients (dolfin and dolfinx).
> > > >
> > > > Some pybind11 patches are already available, will start applying.
> > >
> > > Thanks for the quick pybind11 fix.
> > >
> > > fenicsx-performance-tests failed with MPI errors on some architectures.
> >
> >
> > Not clear yet what's going on with fenicsx-performance-tests. A new release
> > is expected soon, perhaps some of the updates will have fixed tests with
> > PETSc 3.16.
> >
> > fenicsx-performance-tests is at the end of the chain. At this point I
> > recommend just removing fenicsx-performance-tests from testing so as not to
> > hold up the transition while we figure out what's wrong with the performance
> > tests. The dolfinx operational tests (fenics-dolfinx build and debci tests)
> > are passing fine (except s390x which has always been failing debci, and
> > test_sub_bbtree_box reported now at
> > https://github.com/FEniCS/dolfinx/issues/2070). The test_sub_bbtree_box
> > failure is unfortunate but sporadic. I don't think it's worth holding up the
> > transition for it (only one dolfinx test failure in 312, can be skipped
> > temporarily if needed).
> >
> > I'm comfortable removing fenicsx-performance-tests from testing for now.
>
> Alright, removal hint added.
This seems to be done.
Cheers
--
Sebastian Ramacher
--- End Message ---
