On Thu, Oct 26, 2017 at 10:24:57AM +0200, Andreas Tille wrote: > On Tue, Oct 24, 2017 at 02:17:26PM +0200, Sébastien Villemot wrote: > > > (see build log[2]). My suspicion is that this is not really an error in > > > the test suite but some problem with the autobuilder? Could somebody > > > please have a look? If not the only chance I see is to deactivate armhf > > > for pandas. > > > > pandas is uncompiled on armhf, so this is not a blocker for testing migration. > > I can confirm that > > https://packages.debian.org/buster/python-pandas-lib > > does not list armhf but > > https://buildd.debian.org/status/package.php?p=pandas&suite=buster > > lists armhf as "installed". So what is true? What matters is unstable (for outdated binaries), and clearly pandas is not compiled on armhf there: $ rmadison -s unstable python-pandas-lib python-pandas-lib | 0.20.3-10 | unstable | amd64, arm64, armel, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x And the good news is that the new version of pandas has already migrated to testing (it was urgented as part of the python 3.6 transition): $ rmadison -s testing python-pandas-lib python-pandas-lib | 0.20.3-10 | testing | amd64, arm64, armel, i386, mips, mips64el, mipsel, ppc64el, s390x Best, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ http://www.debian.org
Attachment:
signature.asc
Description: PGP signature