[buildd-tools-devel] Bug#834330: says failed to import public key while it tried to import a private one

[Marc Haber]

Package: sbuild
Version: 0.70.0-1
Severity: minor

Hi,

line 1235 in ResolverBase.pm gives the error message "Failed to import
public key". This line, however, covers errors importing a _private_
key. This is most probably a copy-and-paste error.

While we are in this line at the first place, is it possible that this
sbuild only works once and fails every following time because the
private key is already there, gpg --import thus returning 2 and not 0?

I have only seen this behavior when sbuild is being called from
mini-buildd, so this can be a mini-buildd issue. Does standalone
sbuild start over from an empty keyring every time?

Greetings
Marc

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-zgws1 (SMP w/4 CPU cores)
Locale: LANG=en_DK.utf8, LC_CTYPE=en_DK.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sbuild depends on:
ii  adduser         3.115
ii  apt-utils       1.3~pre3
ii  libsbuild-perl  0.70.0-1
pn  perl:any        <none>

Versions of packages sbuild recommends:
ii  debootstrap  1.0.81
ii  fakeroot     1.21-1

Versions of packages sbuild suggests:
pn  deborphan  <none>
ii  wget       1.18-2

-- no debconf information