On 2018-11-06 10:57:12, Holger Levsen wrote:
> On Tue, Nov 06, 2018 at 02:25:37PM +0700, Daniel Kahn Gillmor wrote:
>> On Tue 2018-10-30 11:46:35 -0400, Antoine Beaupré wrote:
>> > 5. backport the required GnuPG patchset from stretch to jessie
>> fwiw, i don't see how this is going to work, since jessie has only gpg
>> 1.4.18 and 2.0.26 -- modern enigmail requires gnupg 2.0.14 at least, so
>> that rules out the 1.4 series. And the 2.0 branch has been EOLed and
>> unsupported upstream for nearly a year, and represents a significantly
>> different codebase than the 2.1/2.2 series.
>>
>> Or if you are talking about backporting 2.1.x or 2.2.x, that might be a
>> different situation; but just backporting the gnupg patches from stretch
>> to jessie sounds pretty tough. (i haven't tried though)
>
> so I'd say this leaves us with two options: a.) getting gnupg 2.1 into
> jessie or b.) declaring thunderbird/enigmail unsupported in jessie.
i think it should be possible to do a) - as "gpg2" of course. it would
require modifications to enigmail to call that binary instead of legacy
1.4, but it might just work without breaking too much stuff as people
probably don't rely on gnupg2 in jessie.
a.
--
Soyons réalistes, faisons l'impossible.
- Ernesto "Che" Guevara
