@osomon: I already saw the proposed link but anyway thanks for summing up the situation.
>From my (user) perspective I like and absolutely agree with the ubuntu principle of not breaking things in favor of chasing higher version numbers but I only see one way out of this dilemma: 'Dropping' those two packages as soon as possible because from your links it seems obvious that they will never be interoperable with newer Thunderbird versions than 68. Has there been any progress in the 50 days since your update got blocked? Looks to me more like a communication problem than a technical problem. Does the SRU team even know that we are desperately waiting for any action from their side? Is there anything else you (or we?) could do to get this ball rolling? Thanks for your time, Olivier! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Triaged Status in thunderbird source package in Focal: Fix Committed Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
