Source: connect-proxy Version: 1.101-1 Severity: serious Tags: stretch sid User: [email protected] Usertags: qa-ftbfs-20160707 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[1]: Entering directory '/«PKGBUILDDIR»' > mkdir -p /«PKGBUILDDIR»/debian/connect-proxy/usr/bin/ > install connect-proxy /«PKGBUILDDIR»/debian/connect-proxy/usr/bin/ > make[1]: Leaving directory '/«PKGBUILDDIR»' > dh_testdir > dh_testroot > dh_installchangelogs > dh_installdocs > dh_installman > dh_link > dh_strip > dh_compress > dh_fixperms > dh_installdeb > dh_shlibdeps > dh_gencontrol > dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is > not NFS-safe > dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is > not NFS-safe > dh_md5sums > dh_builddeb > dpkg-deb: building package 'connect-proxy-dbgsym' in > '../connect-proxy-dbgsym_1.101-1_amd64.deb'. > dpkg-deb: building package 'connect-proxy' in > '../connect-proxy_1.101-1_amd64.deb'. > dpkg-genchanges -sa >../connect-proxy_1.101-1_amd64.changes > dpkg-genchanges: warning: debian/changelog(l17): invalid abbreviated > month name 'Sept' > LINE: -- Philippe Coval <[email protected]> Wed, 20 Sept 2007 23:59:42 +0200 > dpkg-genchanges: warning: debian/changelog(l17): cannot parse > non-comformant date '20 Sept 2007 23:59:42 +0200' > LINE: -- Philippe Coval <[email protected]> Wed, 20 Sept 2007 23:59:42 +0200 > Can't call method "epoch" on an undefined value at > /usr/share/perl5/Dpkg/Changelog.pm line 498. > dpkg-buildpackage: error: dpkg-genchanges gave error exit status 25 > ──────────────────────────────────────────────────────────────────────────────── > Build finished at 20160706-2140 The full build log is available from: http://people.debian.org/~lucas/logs/2016/07/07/connect-proxy_1.101-1_unstable_reb.normal.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.
