Your message dated Sun, 02 Oct 2016 13:51:10 +0000 with message-id <e1bqhac-0002mn...@franck.debian.org> and subject line Bug#839459: fixed in strongswan 5.5.0-3 has caused the Debian Bug report #839459, regarding strongswan: FTBFS: Tests failures to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 839459: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: strongswan Version: 5.5.0-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161001 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): > make[6]: *** [check-recursive] Error 1 > make[6]: Leaving directory '/<<PKGBUILDDIR>>/src/libstrongswan' > Makefile:2131: recipe for target 'check' failed > make[5]: *** [check] Error 2 > make[5]: Leaving directory '/<<PKGBUILDDIR>>/src/libstrongswan' > Makefile:520: recipe for target 'check-recursive' failed > make[4]: *** [check-recursive] Error 1 > make[4]: Leaving directory '/<<PKGBUILDDIR>>/src' > Makefile:580: recipe for target 'check-recursive' failed > make[3]: *** [check-recursive] Error 1 > make[3]: Leaving directory '/<<PKGBUILDDIR>>' > Makefile:869: recipe for target 'check' failed > make[2]: *** [check] Error 2 > make[2]: Leaving directory '/<<PKGBUILDDIR>>' > dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2 > debian/rules:210: recipe for target 'override_dh_auto_test' failed 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/01/strongswan_5.5.0-2_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.
--- End Message ---
--- Begin Message ---Source: strongswan Source-Version: 5.5.0-3 We believe that the bug you reported is fixed in the latest version of strongswan, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 839...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yves-Alexis Perez <cor...@debian.org> (supplier of updated strongswan package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sun, 02 Oct 2016 15:22:54 +0200 Source: strongswan Binary: strongswan libstrongswan libstrongswan-standard-plugins libstrongswan-extra-plugins libcharon-extra-plugins strongswan-starter strongswan-libcharon strongswan-charon strongswan-ike strongswan-nm strongswan-ikev1 strongswan-ikev2 charon-cmd strongswan-pki strongswan-scepclient strongswan-swanctl charon-systemd Architecture: source Version: 5.5.0-3 Distribution: unstable Urgency: medium Maintainer: strongSwan Maintainers <pkg-swan-de...@lists.alioth.debian.org> Changed-By: Yves-Alexis Perez <cor...@debian.org> Description: charon-cmd - standalone IPsec client charon-systemd - strongSwan IPsec client, systemd support libcharon-extra-plugins - strongSwan charon library (extra plugins) libstrongswan - strongSwan utility and crypto library libstrongswan-extra-plugins - strongSwan utility and crypto library (extra plugins) libstrongswan-standard-plugins - strongSwan utility and crypto library (standard plugins) strongswan - IPsec VPN solution metapackage strongswan-charon - strongSwan Internet Key Exchange daemon strongswan-ike - strongSwan Internet Key Exchange daemon (transitional package) strongswan-ikev1 - strongSwan IKEv1 daemon, transitional package strongswan-ikev2 - strongSwan IKEv2 daemon, transitional package strongswan-libcharon - strongSwan charon library strongswan-nm - strongSwan plugin to interact with NetworkManager strongswan-pki - strongSwan IPsec client, pki command strongswan-scepclient - strongSwan IPsec client, SCEP client strongswan-starter - strongSwan daemon starter and configuration file parser strongswan-swanctl - strongSwan IPsec client, swanctl command Closes: 839459 Changes: strongswan (5.5.0-3) unstable; urgency=medium . * debian/control: - add build-dep on tzdata, fix FTBFS when absent. closes: #839459 Checksums-Sha1: 65c5a5b429b2e62ef3c0b4cb4c37e0b553445894 3247 strongswan_5.5.0-3.dsc 5eede61d610f094c28ab989e769461bb5fde07c7 122164 strongswan_5.5.0-3.debian.tar.xz Checksums-Sha256: 8bf97221ba6934e0b1cbd071cfcf39cff383fdf03b9edb102c77eb3753783cd3 3247 strongswan_5.5.0-3.dsc 0c751d6bd5204ce705430a8bab61a571738e78a5a70580705d2c09af7f47e669 122164 strongswan_5.5.0-3.debian.tar.xz Files: 862d486f60b9210b6b40452dc2ea4cdf 3247 net optional strongswan_5.5.0-3.dsc 0c74712dbe2ca00a8a35c4e2db202d87 122164 net optional strongswan_5.5.0-3.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJX8QxMAAoJEG3bU/KmdcCllCsH/R1iQR2L2gFxk/K12fUeA226 JiwPolXQzRpx2vmLA+MBD8F/stxte7CDhfiWd4WEq9jOPXFbsG+hk/LXsfXXrHD9 2OStrMo1xtlvpupiM8Kbx8OwgVw6S7BYCUVe9lR4legbdNxVHjoqLH35P5pnvJet JSeCFXsuXV98NkI7G5AjiBba5wsmkao67nMGjORe6/bOy/edam3kDdpiufhX0X4D 79B4Gq4P2H/KZYjPXaG2Bu2xycMRRi4Rb0AjX1ZgN8FNa3jDplyyHA418xZoyJp9 ZdNDYP6DNCa8NZIWLs1L3adgECB/Rn1Tg9O3SAlqcGsEn2c7YE2uSlkxW27HN3M= =6Pir -----END PGP SIGNATURE-----
--- End Message ---
