Package: python3-h5py Version: 2.10.0-2 Followup-For: Bug #944769 Control: severity -1 important
I don't think this issue warrants severity Serious. The failure is not triggered simply by having no network connection. It is only triggered if there is no network interface at all. The only way there can be no network interface is if the localhost loopback interface lo has been taken down. This is a very artificial situation I think. Ensure that the loopback interface is active with ifup lo -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-h5py depends on: ii libc6 2.29-3 ii libhdf5-openmpi-103 1.10.4+repack-10 ii python3 3.7.5-3 ii python3-mpi4py 3.0.3-1 ii python3-numpy [python3-numpy-abi9] 1:1.17.4-1 ii python3-six 1.13.0-1 python3-h5py recommends no packages. Versions of packages python3-h5py suggests: ii python-h5py-doc 2.10.0-2 -- no debconf information
