Bug#835770: Failure is triggered by fix to #834281
Daniel Kahn Gillmor
dkg at fifthhorseman.net
Wed Sep 14 19:16:10 UTC 2016
Control: reassign 835770 libgnupg-interface-perl 0.52-3
Hi all--
On Wed 2016-09-14 04:17:21 -0400, Sunil Mohan Adapa wrote:
> Recently test cases where failing in libgnupg-interface-perl
> (https://bugs.debian.org/834281) due to gpg binary now defaulting to
> gpg2 in Debian. It was patched to explicitly use 'gpg1' binary instead
> of 'gpg'. This is causing the test suite and monkeysphere to use
> different gpg binaries leading to test case failure.
I think Sunil's diagnosis is correct. gpg1 and gpg in debian unstable
work on different keyrings by default and mixing the two is bound for
trouble.
So the temporary workaround for #834281 is actually causing the failures
in #835770, where everything is expected to use gpg itself.
The fix for this problem, is to drop the workaround and correctly fix
#834281, which i've done by sending patches to upstream's test suite at
https://rt.cpan.org/Ticket/Display.html?id=102651 , and i aim to upload
to debian shortly.
> One solution could be to patch the test suite in Debian to use gpg1
> instead of gpg until monkeysphere and libgnupg-interface-perl support
> gpg2.
I'm really hoping to avoid this kind of thing. let's try to reduce the
dependencies on packages built from src:gnupg1, not extend them.
--dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 930 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20160914/194908ac/attachment-0001.sig>
More information about the pkg-perl-maintainers
mailing list