Source: python-apt
Version: 2.1.7
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat
> -Werror=format-security -g -fwrapv -O2 -g -O2
> -fdebug-prefix-map=/<<PKGBUILDDIR>>=.
> -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat
> -Werror=format-security -Wno-write-strings -DDATE="Dec 10 2020"
> -DTIME="14:35:32" -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -I/usr/include/python3.9 -c python/acquire-item.cc -o
> build/temp.linux-x86_64-3.9/python/acquire-item.o -std=c++11
> -Wno-write-strings -DAPT_8_CLEANER_HEADERS -DAPT_9_CLEANER_HEADERS
> -DAPT_10_CLEANER_HEADERS -DPY_SSIZE_T_CLEAN
> In file included from /usr/include/apt-pkg/deblistparser.h:15,
> from python/apt_pkgmodule.h:19,
> from python/acquire-item.cc:24:
> /usr/include/apt-pkg/pkgcachegen.h:32:10: fatal error: xxhash.h: No such file
> or directory
> 32 | #include <xxhash.h>
> | ^~~~~~~~~~
> compilation terminated.
> error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
> E: pybuild pybuild:353: build: plugin distutils failed with: exit code=1:
> /usr/bin/python3 setup.py build
> dh_auto_build: error: pybuild --build -i python{version} -p 3.9 returned exit
> code 13
> make[1]: *** [debian/rules:20: override_dh_auto_build] Error 25
The full build log is available from:
http://qa-logs.debian.net/2020/12/26/python-apt_2.1.7_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.
