Source: jss Version: 4.6.3-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<<PKGBUILDDIR>>/org/mozilla/jss/pkcs11 && /usr/bin/cc -fPIC > -D_FORTIFY_SOURCE=2 -Wdate-time -Werror=format-security -Wformat > -fstack-protector-strong -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -O2 -g -O2 > -Wall -std=gnu99 -Wno-cast-function-type -Wno-unused-parameter > -Wno-unknown-warning-option -Werror-implicit-function-declaration -Wno-switch > -I/<<PKGBUILDDIR>>/build/include/jss -I/usr/lib/jvm/default-java/include > -I/usr/lib/jvm/default-java/include/linux -I/usr/lib/jvm/default-java/include > -I/usr/include/nspr -I/usr/include/nss -L/usr/lib/x86_64-linux-gnu > -L/usr/lib/x86_64-linux-gnu -o /<<PKGBUILDDIR>>/build/lib/PK11SymKey.o -c > /<<PKGBUILDDIR>>/org/mozilla/jss/pkcs11/PK11SymKey.c > /<<PKGBUILDDIR>>/org/mozilla/jss/pkcs11/PK11SymKey.c: In function > ‘Java_org_mozilla_jss_pkcs11_PK11SymKey_getKeyType’: > /<<PKGBUILDDIR>>/org/mozilla/jss/pkcs11/PK11SymKey.c:265:12: error: > ‘CKM_NETSCAPE_PBE_SHA1_DES_CBC’ undeclared (first use in this function); did > you mean ‘CKM_NSS_PBE_SHA1_DES_CBC’? > 265 | case CKM_NETSCAPE_PBE_SHA1_DES_CBC: > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > | CKM_NSS_PBE_SHA1_DES_CBC > /<<PKGBUILDDIR>>/org/mozilla/jss/pkcs11/PK11SymKey.c:265:12: note: each > undeclared identifier is reported only once for each function it appears in > /<<PKGBUILDDIR>>/org/mozilla/jss/pkcs11/PK11SymKey.c: At top level: > cc1: warning: unrecognized command line option ‘-Wno-unknown-warning-option’ > make[4]: *** [CMakeFiles/generate_c.dir/build.make:224: lib/PK11SymKey.o] > Error 1 The full build log is available from: http://qa-logs.debian.net/2020/06/20/jss_4.6.3-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.
