On Sun, 12 Feb 2017 20:16:06 +0100 Emilio Pozuelo Monfort <pochu@debian .org> wrote: > > > > A binNMU seems to be sufficient here. > > > > nmu petsc_3.7.5+dfsg1-4 . ANY . unstable . -m "Rebuild with openmpi 2.0.2" > > We should probably wait until petsc migrates, and then maybe not do this unless > we unblock openmpi. >
petsc 3.7.5+dfsg1-4 has now hit testing. Unblock for openmpi has been requested in #855217. Please binNMU petsc at your convenience. Drew p.s. I raised the question of the tight openmpi dependency with PETSc authors. They said the tight dependency was put in place so that PETSc would have consistent MPI handling. Otherwise configure, build and runtime of apps using PETSc could all be performed with different mpi versions, which can lead to error especially if the runtime version is older. Moreover mpich does not provide a simple major.minor.subminor decomposition. So the tight dependency on openmpi subminor version was put in place to match the handling used for the single version number available for mpich. But in principle later subminor versions of openmpi should work fine, and so the PETSc authors are putting in place a more relaxed test allowing use with later subminor versions (for the same major.minor). Once this patch is in place (in future versions of petsc), we won't be affected by the same version incompatibility reported here.