Bug#763244: givaro: FTBFS: dh_install: libgivaro-doc missing files (docs/givaro-html/*), aborting

David Suárez david.sephirot at gmail.com
Sun Sep 28 17:18:26 UTC 2014


Source: givaro
Version: 3.7.2-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20140926 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[3]: Entering directory '/«PKGBUILDDIR»'
>  /bin/mkdir -p '/«PKGBUILDDIR»/debian/tmp/usr/bin'
>  /usr/bin/install -c givaro-config givaro-makefile '/«PKGBUILDDIR»/debian/tmp/usr/bin'
>  /bin/mkdir -p '/«PKGBUILDDIR»/debian/tmp/usr/include'
>  /usr/bin/install -c -m 644 givaro-config.h '/«PKGBUILDDIR»/debian/tmp/usr/include'
> make[3]: Leaving directory '/«PKGBUILDDIR»'
> make[2]: Leaving directory '/«PKGBUILDDIR»'
> make[1]: Leaving directory '/«PKGBUILDDIR»'
>    dh_install -O--parallel
> dh_install: libgivaro-doc missing files (docs/givaro-html/*), aborting
> make: *** [binary] Error 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/09/26/givaro_3.7.2-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.



More information about the debian-science-maintainers mailing list