Package: thunderbird
Version: 1:78.1.1-1
Severity: normal
X-Debbugs-Cc: d...@debian.org
User: tails-...@boum.org
Usertags: misc-reported
Hi,
I see that on the debian/experimental branch, where the upgrade to
Thunderbird 78 is being prepared (many thanks for this!), the
thunderbird package has an unversioned "Breaks: enigmail":
commit 8adec8f0bd5eff09cffa8ec8fb579989640e001f
Author: Carsten Schoenert <c.schoen...@t-online.de>
Date: Sat Jun 20 17:04:54 2020 +0200
enigmail: let any version of Enigmail break
The Enigmail functionality for managing OpenPGP keys and encryption is
now included within Thunderbird, means we want to break every existing
enigmal package version so it will get removed by newer thunderbird
packages.
I don't think that's correct: in order to import existing secret keys
from the GnuPG keyring, and previously used Enigmail configuration,
one needs Enigmail 2.2.x (which does nothing more that providing
a migration wizard):
https://wiki.mozilla.org/Thunderbird:OpenPGP:Migration-From-Enigmail.
My own testing, both with and without Enigmail 2.2.x installed,
confirmed this.
So:
1. I think the correct control field for thunderbird would be:
Breaks: enigmail (<< 2:2.2.0~),
2. To support users who currently use Thunderbird + Enigmail in
Debian, ideally we would have Enigmail 2.2.x in Debian at about the
same time as Thunderbird 78, i.e. presumably around 2020-09-22,
when the 68 series will be EOL'ed.
dkg, how likely is it that this happens?
If this does not happen, a plan B could be to set the
mail.openpgp.allow_external_gnupg pref to true by default, so that
Thunderbird's own OpenPGP code falls back to using GnuPG when it
cannot find a secret key it needs.
Thoughts?
Cheers!
