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

Bug#1067064: marked as done (transition: petsc hypre)

Your message dated Wed, 22 May 2024 09:16:44 +0200
with message-id <0628cdd2-6727-4484-bee5-474b8a1b8969@debian.org>
and subject line Re: Bug#1067064: transition: petsc hypre
has caused the Debian Bug report #1067064,
regarding transition: petsc hypre
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.)


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

The petsc patch for the 64-bit time_t transition was deeply invasive.
It makes petsc (and slepc) essentially unmaintainable.

I think the best way to deal with it is to pretend it never happened
and move on with petsc 3.20, upgrading from petsc 3.19.  We'd want to
doing this upgrade anyway.

As part of this transition I'll also upgrade hypre from 2.28.0 to
2.29.0.

I've checked that sundials and getdp build without problem against the
new petsc. dolfinx, dolfin too.

deal.ii builds but fails tests with a reference to undefined
__gmpn_com symbols. This indicates instructions to link to libgmp
didn't get through.  I think this is unrelated to the petsc upgrade,
and I suspect it might be an artifact of my local installation. i.e. I
suspect the build on buildds will be fine. If necessary we can update
deal.ii to take more care linking GMP.


Ben file:

title = "petsc";
is_affected = .depends ~ "libpetsc*3.19" | .depends ~ "libpetsc*3.20";
is_good = .depends ~ "libpetsc*3.20";
is_bad = .depends ~ "libpetsc*3.19";

--- End Message ---
--- Begin Message --- 
On 20/05/2024 11:26, Drew Parsons wrote:

On 2024-05-15 09:20, Sebastian Ramacher wrote:


I think the best way to deal with it is to pretend it never happened
and move on with petsc 3.20, upgrading from petsc 3.19.  We'd want to
doing this upgrade anyway.


Please go ahead.
All uploads have been made now (including dolfin).  Just binNMUs remain (including mshr). 

Everything has migrated. Closing this.

Cheers,
Emilio

--- End Message ---
Reply to: