Source: cfingerd
Version: 1.4.3-3.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 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):
> fakeroot debian/rules binary
> rm -rf debian/tmp
> rm -f debian/{files,substvars}
> test -f stamp-build || /usr/bin/make -f debian/rules build
> install -g root -o root -m 755 -d debian/tmp/DEBIAN
> chmod -R g-ws debian/tmp
> install -g root -o root -m 755 debian/{preinst,postinst,prerm,postrm}
> debian/tmp/DEBIAN/
> install -g root -o root -m 644 debian/conffiles debian/tmp/DEBIAN/
> #
> install -g root -o root -m 755 -d debian/tmp/usr/share/doc/cfingerd
> install -g root -o root -m 644 debian/copyright
> debian/tmp/usr/share/doc/cfingerd/copyright
> install -g root -o root -m 644 debian/changelog
> debian/tmp/usr/share/doc/cfingerd/changelog.Debian
> install -g root -o root -m 644 CREDITS FAQ RECOMMEND TODO
> debian/tmp/usr/share/doc/cfingerd
> install -g root -o root -m 644 CHANGES
> debian/tmp/usr/share/doc/cfingerd/changelog
> install -g root -o root -m 644 README debian/tmp/usr/share/doc/cfingerd/readme
> gzip -9f debian/tmp/usr/share/doc/cfingerd/{changelog.Debian,changelog}
> gzip -9f debian/tmp/usr/share/doc/cfingerd/{readme,CREDITS,FAQ,RECOMMEND,TODO}
> #
> install -g root -o root -m 755 -d debian/tmp/usr/sbin
> install -g root -o root -m 755 -s src/cfingerd debian/tmp/usr/sbin
> install: cannot stat 'src/cfingerd': No such file or directory
> debian/rules:60: recipe for target 'binary-arch' failed
> make: *** [binary-arch] Error 1
The full build log is available from:
http://aws-logs.debian.net/2016/09/10/cfingerd_1.4.3-3.1_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)
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.
