Source: pycryptopp Version: 0.6.0.20120313-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161021 qa-ftbfs Justification: FTBFS on amd64
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 -DNDEBUG -g -fwrapv -O2 -Wall > -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g > -fdebug-prefix-map=/build/python2.7-EkQe1J/python2.7-2.7.12=. > -fstack-protector-strong -Wformat -Werror=format-security -fPIC > -DDISABLE_EMBEDDED_CRYPTOPP=1 -I/usr/include -I/usr/include/python2.7 -c > src/pycryptopp/publickey/ecdsamodule.cpp -o > build/temp.linux-x86_64-2.7/src/pycryptopp/publickey/ecdsamodule.o -w > cc1plus: warning: command line option '-Wstrict-prototypes' is valid for > C/ObjC but not for C++ > In file included from src/pycryptopp/publickey/ecdsamodule.cpp:42:0: > /usr/include/cryptopp/eccrypto.h:19:18: fatal error: hmqv.h: No such file or > directory > #include "hmqv.h" > ^ > compilation terminated. > error: command 'x86_64-linux-gnu-gcc' failed with exit status 1 > debian/rules:25: recipe for target 'build-python2.7' failed > make: *** [build-python2.7] Error 1 If the failure looks somehow time/timezone related: Note that this rebuild was performed without the 'tzdata' package installed in the chroot. tzdata used be (transitively) part of build-essential, but it no longer is. If this package requires it to build, it should be added to build-depends. For the release team's opinion on this, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185 If the failure looks LSB-related: similarly to tzdata, lsb-base is not installed in the build chroot. The full build log is available from: http://aws-logs.debian.net/2016/10/21/pycryptopp_0.6.0.20120313-1_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! 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.
