Bug#782074: RFS: ublock/1.1.1+dfsg-1 [ITP] -- general-purpose lightweight ads, malware, trackers blocker
Hi Matthew,
it is fine to track the origin, but I would add a -origin suffix, to keep it in sync with upstream
name, and to avoid collisions in case somebody else wants to package the fork too.
Moreover lintian is showing a lot of warnings, can you please fix them?
sorry, but I lack of time to properly review it right now.
BTW similar packages (e.g. https-everywhere) didn't create a chrome package, for the below reason as
you linked in the bug), so I might suggest to comment that part, and create a mozilla only version.
It seems to me a security issue to deal with private keys publicly.
cheers,
G.
Il Venerdì 25 Settembre 2015 6:03, Matthew Bekkema <mbekkema97@gmail.com> ha scritto:
I packaged uBlock Origin as suggested by Marius.
Source package: http://mentors.debian.net/debian/pool/main/u/ublock/ublock_1.1.1+dfsg-1.dsc
Mentors page: http://mentors.debian.net/package/ublock
I also enabled the chromium build for this one. debian/uBlock0.pem is a private
key which the .crx file is signed with and is required in order to keep the same
extension ID across rebuilds and upgrades.
More info about this here: http://crbug.com/420373
Reply to: