On 2026-01-20 12:01, Emilio Pozuelo Monfort wrote:
On 20/01/2026 11:52, Drew Parsons wrote:
I think we're ready to transition to hypre 3.0.0.
I see autopkgtest failures for mfem [1]. Can you take a look?
I guess you mean the experimental failures at
https://qa.debian.org/excuses.php?experimental=1&package=hypre
mfem 4.9+ds-2 tested there is the mfem from unstable, built against
hypre 2.33.0.
The test builds a short program using mfem. But mfem headers record the
hypre it was built against, in MFEM_HYPRE_VERSION (in
/usr/include/mfem/config/_config.hpp), and it is used in
/usr/include/mfem/linalg/hypre.hpp to select the hypre-version-dependent
name of seq_mv.h (one of the things that changed in hypre 3).
So mfem built against old hypre can't build tests with new hypre.
Rebuilt against the new hypre, mfem does pass the tests.
I guess we'll find the same problem trying to migrate the new package to
testing.
It means either the old mfem build needs an upper versioned dependency,
or hypre should add a Breaks: mfem.
But it would not be an ongoing problem for mfem, it's only for the
transition to hypre 3 (unless upstream starts making a habit of renaming
header files, but I guess they won't). For that reason I think it would
be more messy to add upper versioned dependency to mfem. Cleaner to add
a Breaks to hypre, since it's the package that's doing the breaking.
Would you like that tested in experimental first, or should we just
proceed with the transition adding the Breaks to the unstable upload?
Drew
