Hello, i added moxext-maintainers, too.
Am 16.10.20 um 19:25 schrieb Adam D. Barratt: > [overrode Reply-To: to keep the list included] > > On Sat, 2020-10-10 at 21:29 +0200, Mechtilde Stehmann wrote: >> I want to clarify one further situation. >> >> Thunderbird 78.3 was uploaded by security team to update from version >> 68.x >> >> Webext-tbsync version 2.11 works fine with thunderbird 68.x. but it >> doesn't work with thunderbird 78.x. >> >> For thunderbird 78.x you need version 2.16 mandatorily. Today I get the information from upstream version 2.16 is broken and version 2.18 is mandatorily >> >> In the meantime there is thunderbird 78.x in buster (security) and >> webext-tbsync version 2.11 in buster. This combination is >> incompatible (broken). >> >> How can we handle such things in a better way in the future? > > This is part of a slightly wider discussion that's come up a few times > before, around the handling of updates to plugins for Mozilla products > (and I guess others, but Firefox and Thunderbird are the ones most > often affected). > > Previous security updates to those packages have led both to packages > being updated in stable (often with large diffs) and other packages > being removed as unsupportable. Is it a better way to provide such uploads (affected by security updates) also via security? Or should I provide them as backports, when they arrived testing? > > There's a school of thought which says that it doesn't make sense to > include the plugins in the Debian archive at all, and we should instead > suggest that users install and update plugins from the upstream > repositories directly. to install plugins from the upstream repository mean that it is installed at /home/<user>/.thunderbird and not system wide. I want to provide an easy system wide installation Kind regards > > Regards, > > Adam > -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
signature.asc
Description: OpenPGP digital signature
