gpgme python bindings release plans?

Ben McGinnes ben at adversary.org
Fri Aug 31 18:31:46 CEST 2018


On Thu, Aug 30, 2018 at 04:33:24PM +0200, Jasper Spaans wrote:
> On 30/08/2018 08:44, Ben McGinnes wrote:
> > I've fixed those conflicts with this commit:
> > 1d00fb987b903e245d484bddfe3c0a0aba670ac1
> >
> > That, however, required changing both of your updates, so you should
> > test it ASAP to see if it still works or whether Ubuntu is going to be
> > a point of pain in future.
> Indeed your fix has broken my build instead.
> 
> (I don't know what Ubuntu has to do with this; and in case my previous
> message was not clear enough: I did not use any Ubuntu-provided versions
> of libgpg-error or gpgme. I wouldn't be surprised if this will cause
> breakage on Debian as well.)

Oh, by the way, when you compiled GPGME and subsequently the Python
bindings, which C compiler did you use: GCC or Clang?  Also which
version of either was used?

What is the output of:  python3.5 -c "import sys; print(sys.version)"


Regards,
Ben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20180901/b5488f26/attachment.sig>


More information about the Gnupg-devel mailing list