[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1016335: muse-el: FTBFS: dh_installdocs: error: Cannot find (any matches for) "examples/QuickStart.pdf" (tried in ., debian/tmp)



Source: muse-el
Version: 3.20+dfsg-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[3]: Entering directory '/<<PKGBUILDDIR>>/lisp'
>   INFO     Scraping files for muse-autoloads.el... 
>   INFO     Scraping files for muse-autoloads.el...done
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/lisp'
> make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    dh_elpa_test
>    create-stamp debian/debhelper-build-stamp
>    dh_prep
>    dh_install
>    dh_elpa
> dh_elpa: warning: missing muse-pkg.el; will try to generate it
>    dh_installdocs
> dh_installdocs: error: Cannot find (any matches for) "examples/QuickStart.pdf" (tried in ., debian/tmp)
> 
> make: *** [debian/rules:4: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/muse-el_3.20+dfsg-6_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220728&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 marking 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: