Bug#1122615: mfem: FTBFS with hypre 3.0 needs new upstream release 4.9
Source: mfem Followup-For: Bug #1122615 X-Debbugs-Cc: Alex Myczko Hi Alex, thanks for the swift upload of mfem 4.9+ds-1 With respect to * d/control: version hypre build-depends I think mfem doesn't need a versioned Build-Depends on hypre 3.0 If I understood correctly, it will still build fine with the older hypre 2, the upstream patch catches the difference with some #ifdefs in code. That is, hypre 3 needs mfem 4.9 (in order to migrate to testing), but mfem 4.9 does not need hypre 3. If we push mfem 4.9 to unstable (once it passes NEW) it can build against hypre 2.33.0, and then it can get rebuilt via a binNMU against hypre 3.0.0 once the hypre transition is started.
Bug#1122615: mfem: FTBFS with hypre 3.0 needs new upstream release 4.9
Source: mfem Version: 4.8+ds-1 Severity: normal Tags: ftbfs fixed-upstream mfem 4.8 fails to build (or build tests) against hypre 3.0.0, now available in experimental: 50s [ 50%] Building CXX object CMakeFiles/ex0.dir/ex0.cpp.o 50s /usr/bin/c++ -isystem /usr/include/hypre -isystem /usr/lib/x86_64-linux-gnu/openmpi/include -isystem /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -MD -MT CMakeFiles/ex0.dir/ex0.cpp.o -MF CMakeFiles/ex0.dir/ex0.cpp.o.d -o CMakeFiles/ex0.dir/ex0.cpp.o -c /tmp/autopkgtest-lxc.ehc41h7j/downtmp/autopkgtest_tmp/cmake/ex0.cpp 51s In file included from /usr/include/mfem/linalg/complex_operator.hpp:18, 51s from /usr/include/mfem/linalg/linalg.hpp:21, 51s from /usr/include/mfem/mfem.hpp:45, 51s from /usr/include/mfem.hpp:2, 51s from /tmp/autopkgtest-lxc.ehc41h7j/downtmp/autopkgtest_tmp/cmake/ex0.cpp:15: 51s /usr/include/mfem/linalg/hypre.hpp:28:10: fatal error: seq_mv.h: No such file or directory 51s28 | #include 51s | ^~ 51s compilation terminated. https://ci.debian.net/packages/m/mfem/unstable/amd64/66935307/#S6 The problem has been fixed upstream in PR#4975 https://github.com/mfem/mfem/pull/4975 and released upstream in v4.9. We'll want to transition hypre to 3.0.0 soon, at which point this bug will become severity serious. Great if the new upstream release can be packaged before.
