Bug#1094821: spglib: autopkgtest failure on 32 bits blocking ruby3.3 transition
Lucas Nussbaum
lucas at debian.org
Thu Feb 6 13:30:32 GMT 2025
On 31/01/25 at 17:14 +0200, Andrius Merkys wrote:
> Hi,
>
> On 2025-01-31 15:54, Lucas Kanashiro wrote:
> > spglib autopkgtest is failing on 32 bits architectures due to some
> > issues with the python test suite:
> >
> > https://ci.debian.net/packages/s/spglib/testing/armel/57276728
> > https://ci.debian.net/packages/s/spglib/testing/armhf/57232534/
> > https://ci.debian.net/packages/s/spglib/testing/i386/57232539/
> >
> > Could you please fix it ASAP? Those failures are blocking the ruby3.3
> > transition (check ruby-defaults tracker page).
>
> This is most likely caused by numpy2 transition. I will try to give it a
> deeper look.
I could reproduce the failure using:
autopkgtest spglib --skip-test=command1 --apt-default-release=trixie --apt-upgrade --add-apt-release=unstable --pin-packages=unstable=src:ruby-defaults,src:spglib -- schroot testing-armhf
It indeed looks like something related to numpy2, independent from the
ruby-defaults transition: the newly built (against unstable) spglib
packages pull in some transitioned packages that break it.
Lucas
More information about the debian-science-maintainers
mailing list