h5py (3.3.0-2) unstable; urgency=medium . * Team upload. * Standards-Version: 4.6.0 h5py (3.3.0-1exp1) experimental; urgency=medium . * Team upload. * New upstream release. h5py (3.2.1-1exp2) experimental; urgency=medium . * Team upload. * Build the hdf5-plugin-lzf package, providing the lzf filter plugin to use the LZF compression library with HDF5. Built for both serial (single processor) jobs (libhdf5-dev) and for multiprocessor (threaded) jobs (libhdf5-mpi-dev). Build-Depends: pkg-config. Closes: #960655. h5py (3.2.1-1exp1) experimental; urgency=medium . * Team upload. * New upstream release. - versioned Build-Depends: cython3 (>= 0.29.15), python3-mpi4py (>= 3.0.3), python3-numpy (>= 1.19.3) * run MPI tests (--with-mpi) with pytest-xvfb switched off (--no-xvfb) pytest-mpi is fragile when pytest-xvfb is loaded, see pytest-mpi upstream Issue #31. * Standards-Version: 4.5.1 h5py (3.1.0-1exp1) experimental; urgency=medium . * Team upload. * New upstream release. * upstream tests now test MPI support via pytest-mpi (--with-mpi) Closes: #941846. * use H5PY_SYSTEM_LZF=1 to build against system lzf. debian patch use_system_lzf.patch still needed to provide path to lzf include dir. h5py (3.0.0-1exp1) experimental; urgency=medium . * Team upload. * New upstream release. - applies debian patches drop_deprecated_dtype_6a77b91.patch drop_deprecation_tests.patch file_default_read_5e71c49.patch fix_2.10_docs.patch remove_deprecated_highlevel_module_2f41c78.patch * Build-Depends: python3-cached-property, python3-pytest-mpi * debhelper compatibility level 13 * Build conditions (serial or mpi) now controlled by environment variables HDF5_MPI, HDF5_PKGCONFIG_NAME * add debian patches - numpy_min_version.patch requires build against minimum numpy versions (not exact versions) - skip_test_selection_assertion.patch uses type name instead of assertIsInstance to check correct Selection objects are generated (since _debian_h5py_{serial,mpi} submodules alter instance path) * setup.py configure rule no longer supported. Use build rule. * don't run build-time tests directly in build dir or else imports aren't done consistently * provide test data_files in tests subdir * make h5py_warnings accessible through toplevel wrapper script