Your message dated Tue, 14 Aug 2018 18:50:00 +0000
with message-id <351920f8-7ab3-16b0-5f3f-939c6c212...@thykier.net>
and subject line Re: libcdio-paranoia: FTBFS in buster/sid (dh_installdocs:
Cannot find "README")
has caused the Debian Bug report #903177,
regarding libcdio-paranoia: FTBFS in buster/sid (dh_installdocs: Cannot find
"README")
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
903177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libcdio-paranoia
Version: 10.2+0.94+2-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
--------------------------------------------------------------------------------
[...]
debian/rules build-arch
dh_testdir
dh_autoreconf
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:80: installing './compile'
configure.ac:28: installing './missing'
example/C++/Makefile.am: installing './depcomp'
[... snipped ...]
Making install in test
make[2]: Entering directory '/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/test'
Making install in cdda_interface
make[3]: Entering directory
'/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/test/cdda_interface'
make[4]: Entering directory
'/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/test/cdda_interface'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory
'/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/test/cdda_interface'
make[3]: Leaving directory
'/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/test/cdda_interface'
Making install in data
make[3]: Entering directory
'/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/test/data'
make[4]: Entering directory
'/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/test/data'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory
'/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/test/data'
make[3]: Leaving directory
'/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/test/data'
make[3]: Entering directory '/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/test'
make[4]: Entering directory '/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/test'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/test'
make[3]: Leaving directory '/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/test'
make[2]: Leaving directory '/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/test'
Making install in example
make[2]: Entering directory '/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/example'
make[3]: Entering directory '/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/example'
make[4]: Entering directory '/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/example'
make[4]: Nothing to be done for 'install-exec-am'.
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/example'
make[3]: Leaving directory '/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/example'
make[2]: Leaving directory '/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/example'
make[2]: Entering directory '/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2'
make[3]: Entering directory '/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2'
make[3]: Nothing to be done for 'install-exec-am'.
/bin/mkdir -p
'/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
/usr/bin/install -c -m 644 libcdio_paranoia.pc libcdio_cdda.pc
'/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
make[3]: Leaving directory '/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2'
make[2]: Leaving directory '/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2'
make[1]: Leaving directory '/<<BUILDDIR>>/libcdio-paranoia-10.2+0.94+2'
dh_testdir
dh_testroot
dh_installchangelogs ChangeLog
dh_installdocs
dh_installdocs: Cannot find (any matches for) "README" (tried in .)
debian/rules:83: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned
exit status 2
--------------------------------------------------------------------------------
The build was made with "dpkg-buildpackage -B" in my autobuilder
but it also fails in reproducible builds:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libcdio-paranoia.html
[ Note: There has been a recent change in debhelper behaviour, the current
behaviour is the intended one. See Bug #903133 for details ].
Thanks.
--- End Message ---
--- Begin Message ---
Source: libcdio-paranoia
Source-Version: 10.2+0.94+2-3
On Sat, 07 Jul 2018 11:40:17 +0000 Santiago Vila <sanv...@debian.org> wrote:
> Package: src:libcdio-paranoia
> Version: 10.2+0.94+2-2
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> I tried to build this package in buster but it failed:
>
> --------------------------------------------------------------------------------
> [...]
Fixed in unstable; bug typo'ed in changelog.
Thanks,
~Niels
--- End Message ---
