Thunderbird flatpak commit subject doesn't show version number
When encountering a problem with a new release and wanting to downgrade back to an older (working) version - especially if some plugin I depend on hasn't been updated yet. The current version is well marked, but it would be helpful if the older versions had a subject line like "Release 115.x.x (github commit id)" so we can do better than walk back one release at a time. All flatpak examples for rollback show meaningful subject lines, but Thunderbird and other flatpaks I actually use don't seem to.
- flatpak remote-info --log flathub app/org.mozilla.Thunderbird
Thunderbird - Thunderbird is a free and open source email, newsfeed, chat, and calendaring client
ID: org.mozilla.Thunderbird
Ref: app/org.mozilla.Thunderbird/x86_64/stable
Arch: x86_64
Branch: stable
Version: 115.9.0
...
Commit: ec99a6e7155ef2ce8fbb88a45c9ce50f3213289cdf6c0f77825b622f30fa7845
Parent: 6e23bd3c0dbb2ea57192a120e9d4c431ee192e454e0cc11452184392f14e6fab
Subject: Export org.mozilla.Thunderbird
Date: 2024-03-19 14:02:18 +0000
History:
Commit: 6e23bd3c0dbb2ea57192a120e9d4c431ee192e454e0cc11452184392f14e6fab
Subject: Export org.mozilla.Thunderbird
Date: 2024-03-05 07:25:45 +0000
Commit: 1d7a72d99a0e77fc16bdd610d356f4eea0626dfaf95fa572744451502b9f4128
Subject: Export org.mozilla.Thunderbird
Date: 2024-03-05 07:04:30 +0000
Все ответы (2)
I know this is not what you want to hear, but Thunderbird has no supported rollback. The profile data files are frequently changed in an update often in the data storage format and there is no way to unchanged them, or revert them.v So making it easier to do something that is not supported is actually going to be a disservice.
On Windows Thunderbird will simply refuse to use the profile that has been updated without a command line override, but I understand some things are not a strictly enforced with Linux.
However, you are welcome to place your feedback/Ideas in the feedback hub. It is linked from the Thunderbird help menu and links to https://connect.mozilla.org/
so always back up the mailbox/metadata before an upgrade? I would say still a good idea to have the version numbers in the subject from a documentation standpoint as you can look up the commits to see if it's worth updating.
Изменено Jeffrey Goh
Для ответа на сообщения вы должны войти в свою учётную запись. Пожалуйста, задайте новый вопрос, если у вас ещё нет учётной записи.