emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#29781: closed (GnuPG 2.0 end-of-life)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#29781: closed (GnuPG 2.0 end-of-life)
Date: Wed, 20 Dec 2017 20:16:07 +0000

Your message dated Wed, 20 Dec 2017 15:15:39 -0500
with message-id <address@hidden>
and subject line Re: [bug#29781] [PATCH 2/2] gnu: python-pygpgme: Use GnuPG 1 
for the test suite.
has caused the debbugs.gnu.org bug report #29781,
regarding GnuPG 2.0 end-of-life
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
29781: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29781
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: GnuPG 2.0 end-of-life Date: Wed, 20 Dec 2017 03:30:24 -0500 User-agent: Mutt/1.9.2 (2017-12-15)
The 2.0 series of GnuPG will stop receiving upstream support at the the
end of the year:

"GnuPG 2.0 is an older branch of GnuPG. This branch will reach end-of-life on
2017-12-31." [0]

These patches adjust the two packages that use gnupg-2.0 to prepare for removing
or deprecating that package.

[0] https://gnupg.org/download/index.html

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- Subject: Re: [bug#29781] [PATCH 2/2] gnu: python-pygpgme: Use GnuPG 1 for the test suite. Date: Wed, 20 Dec 2017 15:15:39 -0500 User-agent: Mutt/1.9.2 (2017-12-15)
On Wed, Dec 20, 2017 at 02:29:02PM +0100, Ludovic Court├Ęs wrote:
> Leo Famulari <address@hidden> skribis:
> 
> > * gnu/packages/gnupg.scm (python-pygpgme, python2-pygpgme)[inputs]: Use 
> > gnupg-1
> > and make it a native-input.
> 
> LGTM!
> 
> BTW, gpgme itself provides Python bindings, which are recommended, I
> think.  Should we build them?

We package them as python-gpg.

However, this PyPi-based package seems to be abandoned by the GPGME
maintainers. At least, it doesn't get updated regularly.

I've been trying to build the bindings as part of the GPGME build, so
that we can get the latest version, but I haven't had time to finish the
work yet.

Once we are able to build the bindings from the latest GPGME, we will be
able to drop the pygpgme package and just use the GPGME bindings for
the package 'alot', which is the only user of pygpgme.

Attachment: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]