Re: enigmail will break with TB upgrade

2018-09-27 Thread Antoine Beaupré
On 2018-09-27 17:27:46, Markus Koschany wrote:
> Am 27.09.18 um 17:12 schrieb Antoine Beaupré:
> [...]
>> I wonder what that was all about...
>> 
>> Was the solution for stretch finally to remove enigmail from stable and
>> use backports?
>
> AFAIK he hasn't made a decision yet and I doubt he will use backports
> because it's not for fixing bugs in stable. ;-) I can only say for
> myself that my private backport of enigmail works on Stretch and I have
> only removed the versioned dependency on gnupg2. If it turns out this is
> not feasible for Jessie, then we should make an announcement with the
> next Firefox update that Firefox addons are no longer supported. However
> I am willing to backport ublock-origin and https-everywhere with my
> maintainer hat on and I believe this is doable.

Yeah, that makes sense for such extensions, but I think gpg is a whole
other ballgame. :)

A.

-- 
In serious work commanding and discipline are of little avail.
 - Peter Kropotkin



Re: enigmail will break with TB upgrade

2018-09-27 Thread Markus Koschany


Am 27.09.18 um 17:12 schrieb Antoine Beaupré:
[...]
> I wonder what that was all about...
> 
> Was the solution for stretch finally to remove enigmail from stable and
> use backports?

AFAIK he hasn't made a decision yet and I doubt he will use backports
because it's not for fixing bugs in stable. ;-) I can only say for
myself that my private backport of enigmail works on Stretch and I have
only removed the versioned dependency on gnupg2. If it turns out this is
not feasible for Jessie, then we should make an announcement with the
next Firefox update that Firefox addons are no longer supported. However
I am willing to backport ublock-origin and https-everywhere with my
maintainer hat on and I believe this is doable.

Markus




signature.asc
Description: OpenPGP digital signature


Re: enigmail will break with TB upgrade

2018-09-27 Thread Antoine Beaupré
On 2018-09-27 17:05:08, Markus Koschany wrote:
> Am 27.09.18 um 04:52 schrieb Antoine Beaupré:
> [...]
>> Enigmail's work, then, might be better targeted at helping the folks in
>> stretch, although I do wonder how we could possibly upgrade GnuPG 2
>> (required to get a new version of Enigmail compatible with TB 60) in
>> jessie without causing all sorts of unrelated trouble. Keep in mind that
>> Jessie still runs the old 2.0 release instead of the (recommended) 2.1
>> (stretch) or 2.2 (buster) releases.
>
> Just for the record. I have backported the Buster version of Enigmail to
> Stretch and it works simply by removing the versioned dependency on
> gnupg2. So far I haven't noticed any issues.

But stretch has GnuPG 2.1 and it's the default gpg binary. jessie will
be a whole other story...

dkg was saying the reason Enigmail used openpgp.js is because gpg was
outdated somehow on some platforms:

 * instead, i realized that the OpenPGP.js node package was only needed
   by enigmail for a few things, in particular to avoid needing a newer
   version of GnuPG.

 * there were a few small changes that needed to be made to GnuPG to
   make enigmail pass its test suites properly without OpenPGP.js, so i
   got them made upstream in GnuPG.

 * then i stripped OpenPGP.js from enigmail, and bumped enigmail's
   dependency on GnuPG.

Source: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909000

I wonder what that was all about...

Was the solution for stretch finally to remove enigmail from stable and
use backports?

A.

-- 
Le pouvoir n'est pas à conquérir, il est à détruire
- Jean-François Brient, de la servitude moderne



Re: enigmail will break with TB upgrade

2018-09-27 Thread Markus Koschany
Am 27.09.18 um 04:52 schrieb Antoine Beaupré:
[...]
> Enigmail's work, then, might be better targeted at helping the folks in
> stretch, although I do wonder how we could possibly upgrade GnuPG 2
> (required to get a new version of Enigmail compatible with TB 60) in
> jessie without causing all sorts of unrelated trouble. Keep in mind that
> Jessie still runs the old 2.0 release instead of the (recommended) 2.1
> (stretch) or 2.2 (buster) releases.

Just for the record. I have backported the Buster version of Enigmail to
Stretch and it works simply by removing the versioned dependency on
gnupg2. So far I haven't noticed any issues.

Markus



signature.asc
Description: OpenPGP digital signature