Bug#968707: thunderbird: Please allow Enigmail 2.2.x with Thunderbird 78
> any idea when Enigmail 2.2.x will finds it's way into unstable? Ubuntu > already is using this version in Groovy Gorilla. > > Thunderbrid 78.2.2 will get released within the next hours and I like to > do a first upload of this version into unstable. But this isn't helpful > as Thunderbird will break now every Enigmail version below 2.2. So the > current installed Enigmail package would get removed. I reported the issue here and provided patches to build the latest version: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970111 Now that Thunderbird is in unstable, this should be addressed as soon as possible...
Bug#968707: thunderbird: Please allow Enigmail 2.2.x with Thunderbird 78
> any idea when Enigmail 2.2.x will finds it's way into unstable? Ubuntu > already is using this version in Groovy Gorilla. Note that the 2.2 addon is not mentioned anywhere on the Enigmail homepage and the Debian watch doesn't detect it either, because it points to the homepage and not the project's Gitlab page. You can find it on https://gitlab.com/enigmail/enigmail/-/tags though.
Bug#968707: thunderbird: Please allow Enigmail 2.2.x with Thunderbird 78
Hello Daniel, any idea when Enigmail 2.2.x will finds it's way into unstable? Ubuntu already is using this version in Groovy Gorilla. Thunderbrid 78.2.2 will get released within the next hours and I like to do a first upload of this version into unstable. But this isn't helpful as Thunderbird will break now every Enigmail version below 2.2. So the current installed Enigmail package would get removed. Am 22.08.20 um 09:48 schrieb Carsten Schoenert: Hello intrigeri, Am 20.08.20 um 15:04 schrieb intrig...@debian.org: 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 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: I've no doubt that this specific on TB packaging side isn't fully ready and will need some fine tuning. My intend in late of May and in the beginning of June was to have a in principle working TB 78 package which is able to write and receive emails. At this time it wasn't clear how the PGP part will move to. But now more than two months later we see much more light and also did get more and more information. So yes, thanks for having a critical look at this. 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. I haven't followed the development of Enigmail in detail, but I assumed that 2.1.x will be the last version of Enigmail which is provided by the Enigmail team. So I'm a bit surprised that Enigmail will do a version 2.2. I'm not really happy about the spreading of news around inclusion of Enigmail functionality into Thunderbird. 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? I trust you enough to add the suggested version to the Breaks entry for enigmail. And I can add this rather quickly as version 78.2.0 is in the door, should be released officially at the beginning of the next week I guess. But of course it would be nice to hear also the opinions of Daniel to this problem. -- Regards Carsten Schoenert
Bug#968707: thunderbird: Please allow Enigmail 2.2.x with Thunderbird 78
Control: tag -1 + pending Hi, Carsten Schoenert (2020-08-22): > I trust you enough to add the suggested version to the Breaks entry for > enigmail. Thank you ⇒ pushed d986a6ddf592336b6c493e6bc30c60b4743fb915.
Bug#968707: thunderbird: Please allow Enigmail 2.2.x with Thunderbird 78
Hello intrigeri, Am 20.08.20 um 15:04 schrieb intrig...@debian.org: > 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 > 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: I've no doubt that this specific on TB packaging side isn't fully ready and will need some fine tuning. My intend in late of May and in the beginning of June was to have a in principle working TB 78 package which is able to write and receive emails. At this time it wasn't clear how the PGP part will move to. But now more than two months later we see much more light and also did get more and more information. So yes, thanks for having a critical look at this. > 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. I haven't followed the development of Enigmail in detail, but I assumed that 2.1.x will be the last version of Enigmail which is provided by the Enigmail team. So I'm a bit surprised that Enigmail will do a version 2.2. I'm not really happy about the spreading of news around inclusion of Enigmail functionality into Thunderbird. > 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? I trust you enough to add the suggested version to the Breaks entry for enigmail. And I can add this rather quickly as version 78.2.0 is in the door, should be released officially at the beginning of the next week I guess. But of course it would be nice to hear also the opinions of Daniel to this problem. -- Regards Carsten Schoenert
Bug#968707: thunderbird: Please allow Enigmail 2.2.x with Thunderbird 78
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 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!
