h5py compares the current version of hdf5 (libhdf5-hl-320,
libhdf5-openmpi-320) against the version it was built against,
and prints a warning message if they don't match
(currently 2.2.0 vs 2.1.0).

libhdf5 is otherwise (supposed to be) ABI compatible,
but it would be better to not have h5py print those warnings,
hence requesting binNMU.

nmu h5py_3.16.0-5 . ANY . unstable . -m "rebuild against HDF5 2.2.0"