[buildd-tools-devel] Bug#792100: sbuild-update --keygen fails if /root/.gnupg didn't exist before

[Wookey]

+++ Johannes Schauer [2015-07-11 11:43 +0200]:
> Source: sbuild
> Version: 0.65.2-1
> Severity: normal
> 
> Hi,
> 
> when running `sbuild-update --keygen` on a fresh system I get:
> 
> $ sudo sbuild-update --keygen
> Generating archive key.
> gpg: keyblock resource `/root/.gnupg/secring.gpg': file open error
> gpg: keyblock resource `/root/.gnupg/pubring.gpg': file open error

Aha. I saw this issue when I installed a new machine recently and
documented sbuild usage. I failed to dig in and find out why it didn't
work in a fresh chroot, or failed to report it (as I obviously got it
working). So well done for folowing through on that. 

> The fix is to just run `sudo mkdir /root/.gnupg` before running
> `sbuild-update --keygen`. Ideally, sbuild-update would run that mkdir
> command itself.

Yes. The package assumes that gnupg has been used already by root on
the system it is run on, which is not necessarily true.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/