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 Ben file: title = "hypre"; is_affected = .depends ~ "libhypre-3.1.0" | .depends ~ "libhypre-301"; is_good = .depends ~ "libhypre-301"; is_bad = .depends ~ "libhypre-3.1.0";
