[BUG REPORT] openSUSE zypper failure with all gpg versions > 2.2.6

James Bottomley James.Bottomley at HansenPartnership.com
Thu Mar 19 16:25:03 CET 2020

On Thu, 2020-03-19 at 08:21 -0700, James Bottomley via Gnupg-devel
> On Thu, 2020-03-19 at 10:11 +0100, Werner Koch wrote:
> > Running
> > 
> >   GPGME_DEBUG=9:/foo/bar/gpgme.log  zypper
> > 
> > should give a large tracefile; I can can have a look at it if you
> > like.
> First reply is stuck in moderation.  This has the compressed gpgme
> log

I should add for the first reply that when I go in and run gpg manually
over exactly the directories and files the gpgme code is using,
verification succeeds, and when I try to do the same thing using a test
programme built on gpgme everything also succeeds, so whatever is
happening seems to be something to do with the sequence of prior
operations zypper did.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20200319/e2b729b2/attachment.sig>

More information about the Gnupg-devel mailing list