[Pkg-mozext-maintainers] privacybadger: Upstream requests regular updates in stable or the removal of the package

[Markus Koschany]

Hi Michael and pkg-mozext-maintainers,

the upstream developer of privacybadger contacted me yesterday and asked
that we upgrade privacybadger in stable to the latest upstream release.
Apparently there were some security and usability fixes that he deems as
very important and he doesn't want that we distribute an older version
which didn't address those issues.

See also

https://github.com/EFForg/privacybadger/issues/2246

I am personally not interested to update privacybadger on a regular
basis in stable when it is apparent that the add-on is simply not
suitable for a stable release. I also don't want to maintain an unstable
version only. He wasn't very specific about the security related bug
fixes, so I can't really determine whether there should be any action
taken.

I see two possible outcomes. We could either remove privacybadger from
stable or update it on a regular basis. Like I said I don't intend to
update privacybadger in stable regularly. There will always be a delay
of two or three months anyway.

At the moment I simply suggest to remove privacybadger from stable and
consequently from unstable/testing as well.

If someone else is interested in the package, we could also try the
regular stable updates. If I don't hear back from anyone I intend to
request the removal of privacybadger from stable and step down as the
co-maintainer.

Regards,

Markus

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-mozext-maintainers/attachments/20200829/c7b2da27/attachment.sig>