Hi! On Mon, 2020-06-29 at 09:19:18 +0900, Norbert Preining wrote: > Package: libdpkg-perl > Version: 1.20.2 > Severity: serious > Justification: breaks unrelated packages
> it seems that the bump to 1.20 changed the behaviour of building > packages, i.e., dpkg-source -b . doesn't work anymore, out of the blue, > due to signature/key import errors: > > $ dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building kig using existing ./kig_20.04.2.orig.tar.xz > dpkg-source: info: building kig using existing ./kig_20.04.2.orig.tar.xz.asc > gpg: public key of ultimately trusted key F3B9C351F80F635D not found > gpg: public key of ultimately trusted key 8ABC9E07886A9BC5 not found > gpg: public key of ultimately trusted key 6CACA448860CDC13 not found > gpg: public key of ultimately trusted key D2BF4AA309C5B094 not found > dpkg-source: error: failed to import key in > kig-20.04.2/debian/upstream/signing-key.asc > $ > > This hasn't been the case before, and I am a bit at loss what needs to > be done. I think this might have been fixed in git already (with the changes to use a different GNUPGHOME directory for the temporary key import), but as I cannot reproduce your problem I'd like to be sure before I upload the current version. I assume you have the key found in the upstream/signing-key.asc in your keyring, perhaps that's even your private key? Maybe this is just a bad interaction with the trustdb or something. :/ Could you try the dpkg from git to see whether that fixes this problem? Thanks, Guillem
