Package: dpkg-dev Version: 1.20.2 Severity: normal Dear Maintainer,
Since dpkg-dev 1.2O.1, dpkg-buildpackage tries to verify tarball signatures from debian/upstream/signing-key.asc with gpg. When called, gpg tries to write a file in $HOME/.gnupg. This is not allowed by default when building with sbuild and pbuilder, and therefore building a package with tarball signatures fails. For instance with gpb buildpackage (calling cowbuilder): dpkg-source -b . dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building libextractor using existing ./libextractor_1.9.orig.tar.gz dpkg-source: info: building libextractor using existing ./libextractor_1.9.orig.tar.gz.asc gpg: Fatal: /nonexistent/.gnupg: directory does not exist! dpkg-source: error: failed to import key in libextractor-1.9/debian/upstream/signing-key.asc dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 According to the gpg manpage, using the gpg option --no-options would prevent gpg from creating ~/.gnupg. Cheers, Bertrand
signature.asc
Description: OpenPGP digital signature
