Bug#1058273: gpredict: FTBFS: dh_install: error: missing files, aborting
Source: gpredict
Version: 2.3-115-g0f3beb6-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<<PKGBUILDDIR>>'
> make[4]: Nothing to be done for 'install-exec-am'.
> /usr/bin/install -c -m 644 ./AUTHORS /<<PKGBUILDDIR>>/debian/tmp/usr/share/gpredict
> /usr/bin/install -c -m 644 ./NEWS /<<PKGBUILDDIR>>/debian/tmp/usr/share/gpredict
> /usr/bin/install -c -m 644 ./README /<<PKGBUILDDIR>>/debian/tmp/usr/share/gpredict
> /usr/bin/install -c -m 644 ./COPYING /<<PKGBUILDDIR>>/debian/tmp/usr/share/gpredict
> make[4]: Leaving directory '/<<PKGBUILDDIR>>'
> make[3]: Leaving directory '/<<PKGBUILDDIR>>'
> make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_install
> dh_install: warning: Cannot find (any matches for) "doc/um/gpredict-user-manual.pdf" (tried in ., debian/tmp)
>
> dh_install: warning: gpredict-doc missing files: doc/um/gpredict-user-manual.pdf
> dh_install: error: missing files, aborting
> make: *** [debian/rules:17: binary] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/gpredict_2.3-115-g0f3beb6-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231212&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
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!
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.
Reply to: