Le 23/03/20 à 12:50, Laurent Bigonville a écrit :
Le 19/03/20 à 18:50, Samuel Thibault a écrit :
Laurent Bigonville, le jeu. 19 mars 2020 18:39:46 +0100, a ecrit:
Le 16/03/20 à 08:38, Guido Günther a écrit :
Dear hurd maintainers,
On Sun, Mar 15, 2020 at 09:05:54AM +0100, Laurent Bigonville wrote:
Source: libhandy
Version: 0.0.12-1
Severity: normal
Hi,
It seems that currently libhandy FTBFS on hurd-i386.
Adding "at-spi2-core [hurd-i386] <!nocheck>" to the
build-dependencies
fixes the problem
Do you have an idea why this does not happen on other platforms? We
don't pull in at-spi2-core there either. Build log is here:
https://buildd.debian.org/status/fetch.php?pkg=libhandy&arch=hurd-i386&ver=0.0.13-1&stamp=1584192605&raw=0
Not too sure TBH
An other option might be to pass NO_AT_BRIDGE=1 as environment
variable,
that /should/ disable the need of at-spi completely
I forgot to comment: I tried building with pbuilder, it went fine both
with and without at-spi2-core. Laurent, did you cross-check that without
at-spi2-core you get the build failure? Possibly the buildds have a
different environment that makes the build somehow fail.
I've no local hurd-i386 machines, but on the porterbox I can reproduce
the issue
Other packages are also FTBFS for the same reason
https://buildd.debian.org/status/fetch.php?pkg=totem&arch=hurd-i386&ver=3.34.1-2&stamp=1570288546&raw=0
