I see that Thunderbird 115.2 is in koji, but it looks like it has not been build for Fedora 38. Is that coming?
https://koji.fedoraproject.org/koji/packageinfo?packageID=39
On Sat, 23 Sep 2023 12:45:41 -0500 steven stern steve@sterndata.com wrote:
I see that Thunderbird 115.2 is in koji, but it looks like it has not been build for Fedora 38. Is that coming?
https://koji.fedoraproject.org/koji/packageinfo?packageID=39
Not the package maintainer, but unlikely. The big jump in version is likely a showstopper for updating stable fedora versions. And, the fact it wasn't built at the same time as F39 and F40 is pretty indicative, as well.
If you aren't going to update to F39 when it is released (it's in beta), then you could download the src.rpm and build it locally if you are willing to take your chances.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
------- Original Message ------- On Sunday, September 24th, 2023 at 06:36, stan via users users@lists.fedoraproject.org wrote:
If you aren't going to update to F39 when it is released (it's in beta), then you could download the src.rpm and build it locally if you are willing to take your chances.
I've been using some of the earlier 115.x builds that showed up for F38 without issue. This morning I built 115.2.2, from the F39 source RPM using mock, and so far it's been running without issue...
Cheers
Adam
On Mon, 2023-09-25 at 16:31 +0000, Adam Mercer via users wrote:
I've been using some of the earlier 115.x builds that showed up for F38 wit= hout issue. This morning I built 115.2.2, from the F39 source RPM using moc= k, and so far it's been running without issue...
Well, I might disagree. Your message was extremely scrambled by the GPG/PGP process.
What I see is mostly unhandled MIME coming through raw. Headers in the message body, mangled body content, undecoded signature MIME content, then two PGP attachments, etc.
Try again, see if it was just a once off.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
------- Original Message ------- On Tuesday, September 26th, 2023 at 09:09, Tim via users users@lists.fedoraproject.org wrote:
Well, I might disagree. Your message was extremely scrambled by the GPG/PGP process.
What I see is mostly unhandled MIME coming through raw. Headers in the message body, mangled body content, undecoded signature MIME content, then two PGP attachments, etc.
Try again, see if it was just a once off.
The email was sent using the Proton Mail webclient and not Thunderbird, so any oddness is not related to Thunderbird.
Cheers
Adam
Hi,
Full-quoted reply, for once, but for a special reason... It was still mangled this time, I've left the whole thing below so you can see what I saw between this reply and my signature. It starts off with an error message, and the message has character encoding (and/or decoding) problems (I see a few =20 sequences in my reader).
On Wed, 2023-09-27 at 23:46 +0000, Adam Mercer via users wrote:
Error verifying signature: Output from gpg2: Hash: SHA256 gpg: armor header: ------- Original Message -------\r\n gpg: unexpected armor: On Tuesday, September 26th, 2023 at 09:09, Tim via users users@lists.fedoraproject.org wrote:\r\n gpg: invalid armor header: Content-Type: application/x-inlinepgp-signed; charset="utf-8" Content-Transfer-Encoding: quoted-printable
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
------- Original Message ------- On Tuesday, September 26th, 2023 at 09:09, Tim via users <users@lists.fedor= aproject.org> wrote:
Well, I might disagree. Your message was extremely scrambled by the GPG/PGP process. =20 What I see is mostly unhandled MIME coming through raw. Headers in the message body, mangled body content, undecoded signature MIME content, then two PGP attachments, etc. =20 Try again, see if it was just a once off.
The email was sent using the Proton Mail webclient and not Thunderbird, so = any oddness is not related to Thunderbird.
Cheers
Adam -----BEGIN PGP SIGNATURE----- Version: ProtonMail
wsBzBAEBCAAnBYJlFL6cCZD5kM/Cme5XlxYhBPznB3C+XnNkqprIuPmQz8KZ 7leXAADe6wf+OITVtDgsul//MHn5Mm+Fl3sH+8qd+lARlTin5M2Awg/2gFPm MQ26il5zVSPT8FSO9b8ov+9wPxEMhDieZONjVeGDcn/wOn9Mf5jv/QRPF2i9 S8yQDPUWEwfwNQuwiada1ZLgdxQkynfuIHOAQeJw9KmskcyIZoBltKA5qNST ZaFOae7t2K/qBqoq3BdGuzfZjTt6rV53bDLCiTFOwaJ/n1aprXI7nwUiHYm/ 76R/JSAiniZjsF94AkNpEeT0KOxK8NFrB1ES/6buAIKxnm7iA1DFs1txdov5 kDg95vvDwqa6bt+WuCwElOmAGp9eg2xa+oZ2ONXk1iKie9V5SNbejw=3D=3D =3Dgjbk -----END PGP SIGNATURE----- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Thu, 2023-09-28 at 13:14 +0930, Tim via users wrote:
Hi,
Full-quoted reply, for once, but for a special reason... It was still mangled this time, I've left the whole thing below so you can see what I saw between this reply and my signature. It starts off with an error message, and the message has character encoding (and/or decoding) problems (I see a few =20 sequences in my reader).
Same here. Also using Evolution.
poc
On 28/9/23 20:32, Patrick O'Callaghan wrote:
On Thu, 2023-09-28 at 13:14 +0930, Tim via users wrote:
Hi,
Full-quoted reply, for once, but for a special reason... It was still mangled this time, I've left the whole thing below so you can see what I saw between this reply and my signature. It starts off with an error message, and the message has character encoding (and/or decoding) problems (I see a few =20 sequences in my reader).
Same here. Also using Evolution.
In Thunderbird V120, I see the same thing a Tim does from Adam's emails except that Thunderbird doesn't throw and error.
regards, Steve
poc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 4/10/23 09:07, Stephen Morris wrote:
On 28/9/23 20:32, Patrick O'Callaghan wrote:
On Thu, 2023-09-28 at 13:14 +0930, Tim via users wrote:
Hi,
Full-quoted reply, for once, but for a special reason... It was still mangled this time, I've left the whole thing below so you can see what I saw between this reply and my signature. It starts off with an error message, and the message has character encoding (and/or decoding) problems (I see a few =20 sequences in my reader).
Same here. Also using Evolution.
In Thunderbird V120, I see the same thing a Tim does from Adam's emails except that Thunderbird doesn't throw and error.
Just further to this, when viewing the mail Thunderbird V120 displays a message above the mail window that says "Only a subset of this message was digitally signed using OpenPGP. If you click the verify button, the unprotected parts will be hidden, and the status of the digital signature will be shown". Having clicked "verify" it displays the message "Reminder: The message shown below is only a subset of the original message", but as far as I can see nothing has changed and it still has the two attachments. When I click on the "OpenPGP Show Message Security" button it displays two messages: *Invalid Digital Signature *This message contains a digital signature, but a technical error was detected. Either the message has been corrupted, or the message has been modified by someone else. *Message is not Encrypted *This message was not encrypted before it was sent. Information sent over the internet without encryption can be seen by other people while in transit.
regards, Steve
regards, Steve
poc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
users mailing list --users@lists.fedoraproject.org To unsubscribe send an email tousers-leave@lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue
Tim wrote:
Adam Mercer wrote:
I've been using some of the earlier 115.x builds that showed up for F38 witout issue. This morning I built 115.2.2, from the F39 source RPM using mock, and so far it's been running without issue...
Well, I might disagree. Your message was extremely scrambled by the GPG/PGP process.
What I see is mostly unhandled MIME coming through raw. Headers in the message body, mangled body content, undecoded signature MIME content, then two PGP attachments, etc.
The problem could be your Evolution. Adam's message seemed just fine when I saw it using exmh.
Dave Close wrote:
Tim wrote:
Adam Mercer wrote:
I've been using some of the earlier 115.x builds that showed up for F38 witout issue. This morning I built 115.2.2, from the F39 source RPM using mock, and so far it's been running without issue...
Well, I might disagree. Your message was extremely scrambled by the GPG/PGP process.
What I see is mostly unhandled MIME coming through raw. Headers in the message body, mangled body content, undecoded signature MIME content, then two PGP attachments, etc.
The problem could be your Evolution. Adam's message seemed just fine when I saw it using exmh.
The problem is that the message uses inline PGP¹ and it does not escape the leading ------- characters which are part of the 'Original Message' delimiter.
Mutt reports the following from gpg when trying to process the message signature:
gpg: unexpected armor: ------- Original Message -------\n gpg: invalid armor header: On Sunday, September 24th, 2023 at 06:36, stan via users users@lists.fedoraproject.org wrote:\n
Mutt does display the message properly then.
There is also an attached public key and then that has a detached signature as well, which seems odd and not likely to be useful. I have no idea why Proton Mail would do that, if it is the mail agent responsible for it.
¹ Technically, the sentence could end there and it would still be reasonably accurate. ;)
On Wed, 2023-09-27 at 17:36 -0700, Dave Close wrote:
The problem could be your Evolution. Adam's message seemed just fine when I saw it using exmh.
It was mangled on two different versions of Evolution on two different Linux distros. It could still be an Evolution problem, but it could also be an authoring problem. Or maybe just a compatibility issue (such as a valid technique that's not widely-enough supported).
On 2023-09-23 10:45, steven stern wrote:
I see that Thunderbird 115.2 is in koji, but it looks like it has not been build for Fedora 38. Is that coming?
https://koji.fedoraproject.org/koji/packageinfo?packageID=39 https://i.imgur.com/bKEMxjt.png
I would probably ask that question in this BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2240134
FESCo approved an exception to the stable update policy: https://pagure.io/fesco/issue/3050
And the f38 branch in git has been updated: https://src.fedoraproject.org/rpms/thunderbird/tree/f38
As far as I can tell, Mozilla has stopped publishing security updates for the 102 series, so I don't think there's any grounds to object to updating to 115 at this point: https://www.thunderbird.net/en-US/thunderbird/releases/
-
Adam Mercer -
Dave Close -
Gordon Messmer -
Patrick O'Callaghan -
stan -
Stephen Morris -
steven stern -
Tim -
Todd Zullinger