Source: intel-ipsec-mb Version: 1.4-2 Severity: minor Tags: trixie sid ftbfs User: [email protected] Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: [email protected] Usertags: qa-doublebuild
Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > --------------------------------------------------------------------------------------------------------------------------------- > > dpkg-buildpackage: info: source package intel-ipsec-mb > dpkg-buildpackage: info: source version 1.4-2 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Colin Ian King > <[email protected]> > dpkg-source --before-build . > debian/rules clean > dh clean > dh_auto_clean > make -j8 clean > make[1]: Entering directory '/<<PKGBUILDDIR>>' > make -C lib clean > make[2]: Entering directory '/<<PKGBUILDDIR>>/lib' > rm -Rf obj > rm -f ./libIPSec_MB_lnk.def > rm -f ./libIPSec_MB.a ./libIPSec_MB.so* ./libIPSec_MB.dll > make[2]: Leaving directory '/<<PKGBUILDDIR>>/lib' > make -C test clean > make[2]: Entering directory '/<<PKGBUILDDIR>>/test' > make -C kat-app clean > make[3]: Entering directory '/<<PKGBUILDDIR>>/test/kat-app' > rm -f main.o gcm_test.o ctr_test.o customop_test.o des_test.o ccm_test.o > cmac_test.o hmac_sha1_test.o hmac_sha256_sha512_test.o hmac_md5_test.o > aes_test.o sha_test.o chained_test.o api_test.o pon_test.o ecb_test.o > zuc_test.o kasumi_test.o snow3g_test.o direct_api_test.o clear_mem_test.o > hec_test.o xcbc_test.o aes_cbcs_test.o crc_test.o chacha_test.o > poly1305_test.o chacha20_poly1305_test.o null_test.o snow_v_test.o > direct_api_param_test.o quic_ecb_test.o hmac_sha1.json.o hmac_sha224.json.o > hmac_sha256.json.o hmac_sha384.json.o hmac_sha512.json.o hmac_md5.json.o > gmac_test.json.o ghash_test.o ghash_test.json.o poly1305_test.json.o > cmac_test.json.o xcbc_test.json.o sha_test.json.o gmac_test.o utils.o imb-kat > ./aes_cbcs_test.d ./aes_test.d ./api_test.d ./ccm_test.d > ./chacha20_poly1305_test.d ./chacha_test.d > ./chained_test.d ./clear_mem_test.d ./cmac_test.d ./cmac_test.json.d > ./crc_test.d ./ctr_test.d ./customop_test.d ./des_test.d > ./direct_api_param_test.d ./direct_api_test.d ./ecb_test.d ./gcm_test.d > ./ghash_test.d ./ghash_test.json.d ./gmac_test.d ./gmac_test.json.d > ./hec_test.d ./hmac_md5.json.d ./hmac_md5_test.d ./hmac_sha1.json.d > ./hmac_sha1_test.d ./hmac_sha224.json.d ./hmac_sha256.json.d > ./hmac_sha256_sha512_test.d ./hmac_sha384.json.d ./hmac_sha512.json.d > ./kasumi_test.d ./main.d ./null_test.d ./poly1305_test.d > ./poly1305_test.json.d ./pon_test.d ./quic_ecb_test.d ./sha_test.d > ./sha_test.json.d ./snow3g_test.d ./snow_v_test.d ./utils.d ./xcbc_test.d > ./xcbc_test.json.d ./zuc_test.d > make[3]: Leaving directory '/<<PKGBUILDDIR>>/test/kat-app' > make -C xvalid-app clean > make[3]: Entering directory '/<<PKGBUILDDIR>>/test/xvalid-app' > rm -f ./ipsec_xvalid.d ./misc.d ./utils.d ipsec_xvalid.o misc.o utils.o > imb-xvalid > make[3]: Leaving directory '/<<PKGBUILDDIR>>/test/xvalid-app' > make -C fuzz-app clean > make[3]: Entering directory '/<<PKGBUILDDIR>>/test/fuzz-app' > rm -f imb-fuzz-api imb-fuzz-direct-api > make[3]: Leaving directory '/<<PKGBUILDDIR>>/test/fuzz-app' > make -C acvp-app clean > make[3]: Entering directory '/<<PKGBUILDDIR>>/test/acvp-app' > rm -f ./utils.d imb-acvp > make[3]: Leaving directory '/<<PKGBUILDDIR>>/test/acvp-app' > make -C wycheproof-app clean > make[3]: Entering directory '/<<PKGBUILDDIR>>/test/wycheproof-app' > rm -f aes_gcm_test.json.o aes_ccm_test.json.o chacha20_poly1305_test.json.o > aes_cmac_test.json.o gmac_test.json.o gmac_test.json.o hmac_sha1_test.json.o > hmac_sha224_test.json.o hmac_sha256_test.json.o hmac_sha384_test.json.o > hmac_sha512_test.json.o wycheproof.o *.d imb-wycheproof > make[3]: Leaving directory '/<<PKGBUILDDIR>>/test/wycheproof-app' > make[2]: Leaving directory '/<<PKGBUILDDIR>>/test' > make -C perf clean > make[2]: Entering directory '/<<PKGBUILDDIR>>/perf' > rm -f ipsec_perf.o msr.o misc.o > rm -f ipsec_perf.d msr.d misc.d > rm -f imb-perf > make[2]: Leaving directory '/<<PKGBUILDDIR>>/perf' > make -C examples clean > make[2]: Entering directory '/<<PKGBUILDDIR>>/examples' > make -C burst-app clean > make[3]: Entering directory '/<<PKGBUILDDIR>>/examples/burst-app' > rm -f main.o imb-burst > make[3]: Leaving directory '/<<PKGBUILDDIR>>/examples/burst-app' > make[2]: Leaving directory '/<<PKGBUILDDIR>>/examples' > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_clean > dh_makeshlibs > dh_shlibdeps > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building intel-ipsec-mb using existing > ./intel-ipsec-mb_1.4.orig.tar.xz > dpkg-source: error: cannot represent change to test/acvp-app/utils.o: binary > file contents changed > dpkg-source: error: add test/acvp-app/utils.o in > debian/source/include-binaries if you want to store the modified binary in > the debian tarball > dpkg-source: error: unrepresentable changes to source > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 1 > > E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage > --sanitize-env -us -uc -rfakeroot -S' failed to run. The full build log is available from: http://qa-logs.debian.net/2023/08/13/intel-ipsec-mb_1.4-2_unstable.log If you reassign this bug to another package, please mark 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 mine so that we can identify if something relevant changed in the meantime.

