Bug#1141559: transition: hypre
Emilio Pozuelo Monfort <[email protected]>
| Newsgroups | gmane.linux.debian.devel.release |
|---|---|
| Message-ID | <d8938707-b55c-4575-a133-2eceb79d2b4a__30278.8200600602$1784016092$gmane$org@debian.org> |
Control: tags -1 confirmed On 06/07/2026 10:30, Drew Parsons wrote: > Package: release.debian.org > Severity: normal > X-Debbugs-Cc: [email protected] > Control: affects -1 + src:hypre > User: [email protected] > Usertags: transition > > Loss of functionality in autoconf package builds means debian can no > longer easily build MPI packages via autoconf. > Apparently debhelper 13.32 is to blame, cf. Bug#1139889. > > In the case of hypre the simplest workaround is to abandon autoconf > and start using cmake. hypre's cmake configuration uses a particular > idiosyncratic formula to set the SONAME ABI, which wasn't used with > autoconf. So we need this transition to switch over to the cmake soname. > > The code is the same and the file layout is the same (a new cmake > config becomes available, but we didn't have it before). > So dependent packages can build the same way as before. The only > difference is the change in the value of the soname. > > petsc would be removed with hypre removal (RC Bug#1139536), > and removal of petsc4py might impact the python transition, > removing a bundle of other dependent python packages. > For that reason it might be prudent to give this transition priority, > to help the python transition proceed smoothly at the level of the > numerical (finite element) python packages. > > https://release.debian.org/transitions/html/auto-hypre.html Go ahead. Cheers, Emilio