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 Cheers, -- Guido > > Kind regards, > Laurent Bigonville > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, > 'experimental-debug'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) > Kernel taint flags: TAINT_FIRMWARE_WORKAROUND > Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), > LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy >
