[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1042005: marked as done (transition: mumps hypre2.28.0 superlu combblas)

Your message dated Sun, 10 Sep 2023 10:49:02 +0200
with message-id <ZP2C/k4p3WVyysfV@ramacher.at>
and subject line Re: Bug#1042005: Info received (Bug#1042005: transition: mumps hypre2.28.0 superlu combblas)
has caused the Debian Bug report #1042005,
regarding transition: mumps hypre2.28.0 superlu combblas
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 owner@bugs.debian.org
immediately.)


-- 
1042005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042005
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
X-Debbugs-Cc: mumps@packages.debian.org, debian-science@lists.debian.org
Control: affects -1 + src:mumps

I'd like clear out some transitions in the numerical library stack:

combblas:  1.16.0 → 2.0.0
superlu:        5 → 6
hypre:     2.26.0 → 2.28.0
mumps:        5.5 → 5.6

I want to bump hypre to 2.28.0 not 2.29.0
since PETSc cannot yet use hypre 2.29.0.

I do not want to bump PETSc to 3.19 yet, because of errors
with dolfin (#1042000) and dolfinx (#1042003).

Each package has auto-transitions:
https://release.debian.org/transitions/html/auto-combblas.html
https://release.debian.org/transitions/html/auto-superlu.html
https://release.debian.org/transitions/html/auto-hypre.html  (albeit for 2.29.0)
https://release.debian.org/transitions/html/auto-mumps.html

Ben file:

title = "hypre";
is_affected = .depends ~ /\b(libhypre\-2\.28\.0|libhypre64\-2\.28\.0|libhypre64m\-2\.28\.0|libhypre\-2\.26\.0|libhypre64\-2\.26\.0|libhypre64m\-2\.26\.0)\b/
is_good = .depends ~ /\b(libhypre\-2\.28\.0|libhypre64\-2\.28\.0|libhypre64m\-2\.28\.0)\b/
is_bad = .depends ~ /\b(libhypre\-2\.26\.0|libhypre64\-2\.26\.0|libhypre64m\-2\.26\.0)\b/

title = "mumps";
is_affected = .depends ~ "libmumps-5.5" | .depends ~ "libmumps-5.6";
is_good = .depends ~ "libmumps-5.6";
is_bad = .depends ~ "libmumps-5.5";

--- End Message ---
--- Begin Message --- 
On 2023-09-04 17:59:32 +0000, Graham Inggs wrote:
> Hi
> 
> On Thu, 31 Aug 2023 at 12:03, Sebastian Ramacher <sramacher@debian.org> wrote:
> > Unfortunately trilinos is a key package and so cannot be removed without
> > much effort from testing to complete the transition. Can you please take
> > a look at fixing the current issues with trilinos?
> 
> As can be seen on salsa [1], packaging of trilinos 14.4.0-1 is
> underway, although it is taking a bit longer than expected.
> 
> In the meantime, I've uploaded trilinos 13.2.0-5 to unstable, which
> should fix the build with GCC-13.

Thanks!

The old binaries got removed from testing. Closing.

Cheers
-- 
Sebastian Ramacher

--- End Message ---
Reply to: