Debian Bug report logs - #806661
tor: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Santiago Vila <sanvila@debian.org>

To: Debian BTS <submit@bugs.debian.org>

Subject: tor: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

Date: Sun, 29 Nov 2015 20:25:17 +0000

Package: src:tor
Version: 0.2.7.5-1
User: sanvila@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:

--------------------------------------------------------------------------------
[...]
 debian/rules build-indep
dh \
	build-indep \
	--with quilt \
	--with autoreconf \
	--with systemd \
	--builddirectory=build \
	--parallel
   dh_testdir -i -O--builddirectory=build -O--parallel
   dh_quilt_patch -i -O--builddirectory=build -O--parallel
Applying patch 20-upstream-syslog-identity
patching file changes/bug17194

[... snipped ...]

rm -f micro-revision.tmp; \
if test -d "../.git" && \
		test -x "`which git 2>&1;true`"; then \
	HASH="`cd ".." && git rev-parse --short=16 HEAD`"; \
	echo \"$HASH\" > micro-revision.tmp; \
fi; \
if test ! -f micro-revision.tmp; then \
	if test ! -f micro-revision.i; then \
		echo '""' > micro-revision.i; \
	fi; \
elif test ! -f micro-revision.i || \
		test x"`cat micro-revision.tmp`" != x"`cat micro-revision.i`"; then \
	mv micro-revision.tmp micro-revision.i; \
fi; \
rm -f micro-revision.tmp; \
true
 /bin/mkdir -p '/<<PKGBUILDDIR>>/debian/tmp/usr/bin'
  /usr/bin/install -c src/or/tor src/tools/tor-resolve src/tools/tor-gencert '/<<PKGBUILDDIR>>/debian/tmp/usr/bin'
 /bin/mkdir -p '/<<PKGBUILDDIR>>/debian/tmp/usr/bin'
 /usr/bin/install -c ../contrib/client-tools/torify '/<<PKGBUILDDIR>>/debian/tmp/usr/bin'
 /bin/mkdir -p '/<<PKGBUILDDIR>>/debian/tmp/etc/tor'
 /usr/bin/install -c -m 644 src/config/torrc.sample '/<<PKGBUILDDIR>>/debian/tmp/etc/tor'
 /bin/mkdir -p '/<<PKGBUILDDIR>>/debian/tmp/usr/share/doc/tor'
 /usr/bin/install -c -m 644 doc/tor.html doc/tor-gencert.html doc/tor-resolve.html doc/torify.html '/<<PKGBUILDDIR>>/debian/tmp/usr/share/doc/tor'
 /bin/mkdir -p '/<<PKGBUILDDIR>>/debian/tmp/usr/share/man/man1'
 /usr/bin/install -c -m 644 doc/tor.1 doc/tor-gencert.1 doc/tor-resolve.1 doc/torify.1 '/<<PKGBUILDDIR>>/debian/tmp/usr/share/man/man1'
 /bin/mkdir -p '/<<PKGBUILDDIR>>/debian/tmp/usr/share/tor'
 /usr/bin/install -c -m 644 ../src/config/geoip ../src/config/geoip6 '/<<PKGBUILDDIR>>/debian/tmp/usr/share/tor'
make[2]: Leaving directory '/<<PKGBUILDDIR>>/build'
make[1]: Leaving directory '/<<PKGBUILDDIR>>/build'
   debian/rules override_dh_install
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_install --fail-missing
mv debian/tor/etc/tor/torrc.sample debian/tor/etc/tor/torrc
mv: cannot stat 'debian/tor/etc/tor/torrc.sample': No such file or directory
debian/rules:63: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
debian/rules:23: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit status 2
--------------------------------------------------------------------------------

Sorry not to have a fix, as I am reporting many bugs similar to
this one. The common hints are:

* If the only architecture-independent packages are dummy transitional
ones and they were released with jessie, the easy fix is to drop them
now.

* When using "dh", it is allowed to use (independently)
optional targets override_dh_foo-arch and override_dh_foo-indep
(for several values of "foo").


Once that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, the package would be suitable to be uploaded in source-only
form if you wish.

Thanks.

Message #12 received at 806661@bugs.debian.org (full text, mbox, reply):

From: Santiago Vila <sanvila@unex.es>

To: Peter Palfrader <weasel@debian.org>

Cc: 806661@bugs.debian.org

Subject: Re: tagging 806661

Date: Wed, 13 Jul 2016 22:42:15 +0200 (CEST)

Greetings.

I have the ok from the Release Managers to consider this issue
as RC for stretch.

I'm going to wait a week before raising severities, but since this bug
is in pending state, I'd appreciate if you could make an upload
before that.

Thanks.

Message #17 received at 806661@bugs.debian.org (full text, mbox, reply):

From: Peter Palfrader <weasel@debian.org>

To: Santiago Vila <sanvila@unex.es>

Cc: 806661@bugs.debian.org

Subject: Re: tagging 806661

Date: Wed, 13 Jul 2016 21:31:57 +0000

On Wed, 13 Jul 2016, Santiago Vila wrote:

> I have the ok from the Release Managers to consider this issue
> as RC for stretch.
> 
> I'm going to wait a week before raising severities, but since this bug
> is in pending state, I'd appreciate if you could make an upload
> before that.

It's fixed in 0.2.7.6-2, which hasn't been uploaded to unstable but
which is included in 0.2.8.5-rc-1 from experimental.

I expect the version from experimental will make it to unstable in the
next few weeks.

Cheers,
-- 
                            |  .''`.       ** Debian **
      Peter Palfrader       | : :' :      The  universal
 https://www.palfrader.org/ | `. `'      Operating System
                            |   `-    https://www.debian.org/

Message #22 received at 806661@bugs.debian.org (full text, mbox, reply):

From: Santiago Vila <sanvila@unex.es>

To: Peter Palfrader <weasel@debian.org>

Cc: 806661@bugs.debian.org

Subject: Re: tagging 806661

Date: Thu, 14 Jul 2016 00:26:32 +0200 (CEST)

On Wed, 13 Jul 2016, Peter Palfrader wrote:

> It's fixed in 0.2.7.6-2, which hasn't been uploaded to unstable but
> which is included in 0.2.8.5-rc-1 from experimental.
> 
> I expect the version from experimental will make it to unstable in the
> next few weeks.

Well, since 0.2.7.6-2 < 0.2.8.5, you could still upload 0.2.7.6-2
(in git, I suppose) for unstable if you wish, and nobody will tell you
that you should not do that. If the bug is actually fixed, you can
even make a source-only upload with "dpkg-buildpackage -S".

But of course it's up to you.

Thanks.

Message #29 received at 806661-done@bugs.debian.org (full text, mbox, reply):

From: Peter Palfrader <weasel@debian.org>

To: 806661-done@bugs.debian.org

Subject: Re: Bug#806661: tagging 806661

Date: Mon, 8 Aug 2016 08:44:31 +0000

Version: 0.2.7.6-2

On Wed, 13 Jul 2016, Peter Palfrader wrote:

> On Wed, 13 Jul 2016, Santiago Vila wrote:
> > I'm going to wait a week before raising severities, but since this bug
> > is in pending state, I'd appreciate if you could make an upload
> > before that.
> 
> It's fixed in 0.2.7.6-2, which hasn't been uploaded to unstable but
> which is included in 0.2.8.5-rc-1 from experimental.
> 
> I expect the version from experimental will make it to unstable in the
> next few weeks.

The 0.2.8.x tree is now in unstable.

-- 
                            |  .''`.       ** Debian **
      Peter Palfrader       | : :' :      The  universal
 https://www.palfrader.org/ | `. `'      Operating System
                            |   `-    https://www.debian.org/

Send a report that this bug log contains spam.