Bug#1080198: h5py: autopkgtest regressions with mpich as default provider on 32 bit architectures

Chris Hofstaedtler zeha at debian.org
Sat Nov 9 11:00:40 GMT 2024


On Sat, Aug 31, 2024 at 12:33:26PM +0000, Graham Inggs wrote:
> Since the upload of mpi-defaults 1.17, the autopkgtests of h5py have
> regressed on 32-bit architectures [1]:  I've copied what I hope is the
> relevant part of the log below.

Pinging this bug as 3.11.0-8 doesn't migrate, due to autopkgtest
regressions in python-meshio:

autopkgtest for python-meshio/7.0.0-really-5.3.5-3: amd64: Pass, arm64: Regression or new test ♻ (reference ♻), armel: Pass, armhf: Pass, i386: Pass, ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)

Looks like there is an instabillity problem with regards to
python3-dolfin:

 23s The following packages have unmet dependencies:
139
 23s  python3-dolfin : Depends: python3-dolfin-real but it is not installable or
140
 23s                            python3-dolfin64-real but it is not installable
141
 23s  satisfy:command-line : Depends: python3-dolfin-real but it is not installable
142
 23s E: Unable to correct problems, you have held broken packages.
143
 23s test-meshio          FAIL badpkg



More information about the debian-science-maintainers mailing list