Source: xfonts-75dpi Version: 1:1.0.4+nmu1 Severity: serious Justification: FTBFS on arm64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201205 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on arm64 (I don't know if it also fails on amd64). Relevant part (hopefully): > checking pkg-config is at least version 0.9.0... yes > yes > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > Invalid configuration `aarch64-linux-gnu': machine `aarch64' not recognized > configure: error: /bin/bash ../font-adobe-75dpi/config.sub aarch64-linux-gnu > failed > checking build system type... checking build system type... yes > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... Invalid configuration > `aarch64-linux-gnu': machine `aarch64' not recognized > yes > configure: error: /bin/bash ../font-bh-75dpi/config.sub aarch64-linux-gnu > failed > Invalid configuration `aarch64-linux-gnu': machine `aarch64' not recognized > configure: error: /bin/bash ../font-bitstream-75dpi/config.sub > aarch64-linux-gnu failed > make: *** [debian/rules:41: debian/stamps/build-font-adobe-75dpi] Error 1 > make: *** Waiting for unfinished jobs.... > checking build system type... make: *** [debian/rules:41: > debian/stamps/build-font-bitstream-75dpi] Error 1 > make: *** [debian/rules:41: debian/stamps/build-font-bh-75dpi] Error 1 > Invalid configuration `aarch64-linux-gnu': machine `aarch64' not recognized > configure: error: /bin/bash ../font-bh-lucidatypewriter-75dpi/config.sub > aarch64-linux-gnu failed The full build log is available from: http://qa-logs.debian.net/2020/12/05/xfonts-75dpi_1.0.4+nmu1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.