[buildd-tools-devel] Bug#843137: Bug#843137: sbuild: fails to deal with sid chroots (missing gpg)

[Johannes Schauer]

Control: fixed -1 0.67.0

Hi,

Quoting Cyril Brulebois (2016-11-04 07:04:10)
> Package: sbuild
> Version: 0.65.2-1
> Severity: serious
> Justification: fails to work in the most trivial case
> 
> Hi,
> 
> a brand new unstable chroot isn't usable for a build with default (as
> far as I can remember) sbuild configuration. Full log follows:
> [...]
> | Merged Build-Depends: build-essential, fakeroot
> | Filtered Build-Depends: build-essential, fakeroot
> | dpkg-deb: building package 'sbuild-build-depends-core-dummy' in '/«BUILDDIR»/resolver-ANKNBn/apt_archive/sbuild-build-depends-core-dummy.deb'.
> | E: Failed to execute “gpg”: No such file or directory
> | Failed to sign dummy archive Release file.

the version you specified seems to indicate that you are using sbuild from
Jessie. That version expects gpg to be installed inside the chroot. In the past
(before apt 1.3~exp1) apt would depend on gnupg and thus every chroot would
automatically have gpg installed. So this is why your Debian unstable chroot
doesn't come with gpg. The problem is fixed since sbuild 0.67.0 which makes
signing the internal dummy repository optional.

Unfortunately, for other reasons, you have to start using sbuild from backports
if you want to build in a Debian unstable chroot. The reason for that is that
even if you now manually install gpg into your chroot, the gnupg version will
add several incompatibilities which are also only addressed in more recent
sbuild releases.

Thanks!

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20161104/ee5ff645/attachment-0001.sig>