Still version 115.9.0, when 115.11.0 exists?
https://bodhi.fedoraproject.org/updates/?packages=thunderbird
Here is the repo, as I understand. Or should we use flathub version instead?
Same out od date…
I am on F39 and TB is 115.11.0.
Apparently, it fails to build for Fedora 40:
https://koji.fedoraproject.org/koji/packageinfo?packageID=39
2 Likes
Should we alert someone? If yes - how?
Past 6-8 months I take all as flathub and switch all pre installed to flathub too just seen so many Fedora hosted flatpaks out of date so easier just switch to flathub much easier and no need to worry does it get updated or not and when
It seams there is a solution in Bugzilla on mozilla . org :
1 Like
Added package-maintainers
How is the migration to flatpak version sholud go? I know the profile will be stored in a different place. I have ~60 gb of mails, do not want to download it again from scratch.
Be patient, Firefox will be updated as soon the bug-fix is integrated into the package for F40.
I added the package-maintainers tag to the topic, so they see that there is action needed that the build process is not failing anymore.
1 Like
Good catch, as Claude.ai would say.
My TB is 115.10.1 (Flatpak). Just for kicks, I checked BetterBird, the soft fork, and they are on 115.11.0.
I may run them in parallel for a while to see which one has the best performance. I already noticed it has multiple subject lines, which would be helpful.
Since BB say they closely follow the Thunderbird ESR release schedules, I think BB will have the same security patches as Thunderbird. BB is supposedly “built from the latest version of Thunderbird ESR before applying its own fixes, features and customisations”. Maybe to get 115.11 BB is worth a try.
1 Like
The issue is known and the maintainer already takes care:
https://bugzilla.redhat.com/show_bug.cgi?id=2261180#c7
The maintainer also already started a discussion about it in the devel mailing list.
Let’s give them some time.
I am not involved with that package, but at this time, it seems not even clear if that issue is in Fedora or if the failed builds indicate an issue that is upstream, so in thunderbird 115.10 & .11.
6 Likes
New builds are now in preparation. According to what I read in the devel mailing list, they shall solve the problem of the failed preceding builds and thus hopefully be available soon. They are 115.11 for f40 and f41.
→ thunderbird-115.11.0-1.fc40
With some luck, you will find them in bodhi soon and soon later in your stable updates 
3 Likes
thunderbird-115.11.0-1.fc40 has reached bodhi: Feel encouraged to contribute to testing - once three people have tested the new Thunderbird and confirmed in bodhi that it works fine (which means, adding +1 Karma through a comment in bodhi - so a green thumbs up at Karma and then submit it along with a comment, see bottom of the bodhi page), the maintainer can push it to stable before 7 days have passed.
So you can fasten the process for yourself and for everyone
How to test:
In the bodhi page (at the top), a command on yellow background will appear in a few hours. With this command, you can install the build. This command will NOT enable testing repositories permanently or generally but only install this one build from testing and its dependencies. Architecture and such will be resolved automatically. You can just use the command as it will be.
Bodhi page: FEDORA-2024-7ade906120 — security update for thunderbird — Fedora Updates System
Although it is very unlikely that issues occur after the automated tests have been finished (which is the requirement for the “yellow command” to appear), we formally suggest to not use production instances for testing. E.g., use a VM or a blank thunderbird that does not contain critical data.
→ the automated bodhi tests might show from time to time an error in the automated tests (it does it at the moment for example), but you can ignore that. These errors will be resolved and do NOT imply that the build has failed again or so. It is unlikely at this stage that errors occur that further delay the update.
3 Likes
Thanks to inform us.
I guess for an application I do not have to activate the whole testing repository, i just can test one application.
Do you know how to add this way an app/repo and remove after testing ?
1 Like
Just use the command as it appears, once it appears. It will only get the very package and its dependencies from testing, and then testing will be disabled again. E.g., the thunderbird will be pushed from testing to stable while it is installed on your machine (so no need to make further actions at that time), and the next thunderbird update will then be pulled again from stable and not from testing.
1 Like
I missed that alias I responded to early 
Let me see if it is there now …
1 Like
The yellow-backgrounded command is available and we have already two karma. Feel free to add another one Making some use of bodhi, koji and so on also offers a good opportunity to get some feeling how the later stages of our testing work.
Some issues in a spec file seem to remain persistently, but there is hope they are not relevant (the related tests ain’t required to push the build to stable) so that the maintainer can push the package soon, maybe even today I hope these spec issues are related to i386 lib issues, which we don’t support and thus don’t use anyway 