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

Re: Bug#897642: RFS: gpgme1.0/1.11.1-1~bpo9+1


Am 09.09.18 um 07:55 schrieb Roger Shimizu:
> Both gpgme1.0 and libgpg-error are already in backports NEW queue.
> So I'm closing this ticket.
>> Thank you>> Looking into why you did a gnupg2 backport I probably should use
>> that too, to support newer ECC keys.>
> Please do so.
> Thanks for your work!

please talk before doing a backport to the release team if they would
accept in circumstances gnupgp2 within a point release, supporting
recent gpg key material is something which can also being seen as a
security fix, and that's the point releases are for, not backports.
Given that Stretch is quite young in a possible lifespan of four years I
bet gnupg2 will need at one for Stretch obviously.

It's already (to?) late for enigmail e.g., Thunderbird 60.0 has a Breaks
on Enigmail < 2 and enigmail will need gnupg2. Thunderbird 60.0 has
taken the NEW queue for s-s a few days ago. Time is passing by ...

So people can use the recent Enigmail extension from
https://addons.thunderbird.net/ of course but don't get support for new
keys I guess as s-s don't get a recent enigmail package which is
requiring gnupg2.

Note: I'm not that deep in the impact of an introduction of gnupg2, so I
might have not a realistic view on this all. I just see that we once
again have made our self a hard time with the release of a new ESR
version of Thunderbird like for 45 and 52 in the past.

Carsten Schoenert

Reply to: