Source: glib2.0 Version: 2.54.2-1 Severity: serious As can be seen at https://buildd.debian.org/status/logs.php?pkg=glib2.0&arch=arm64 glib2.0 FTBFS on arm64 quite often.
Looking through the build history, arm-arm-04 (and to a lesser extent arm-arm-01) seems to be much more susceptible to build failures. I only count one successful build but 5 failed builds for arm-arm-04. When the build was retried on a different host, it seems to have succeeded in the past. Running the build on a porter box (amdahl), I was able to successfully compile the package. Afaics, arm-arm-01 and arm-arm-04 are slower hosts judging by the build times. Maybe that contributes to the test suite failures. As the glib2.0 maintainers don't have access to those systems (or slower arm buildds), it would be great if the arm porters can investigate this. Given the importance of glib2.0, having reliable builds on arm64 would be good. Thanks in advance, Michael -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)