Packaging request #1873
[firefox-extension-privacybadger] Requires blacklisted firefox
Status:
open
Priority:
broken
Assignee:
% Done:
0%
Description
So it should either be removed, or replaced with liberated package for iceweasel.
I wonder if the alternative can be just to add provides=("firefox") to the PKGBUILD of iceweasel. Not sure though about negative implications of this, and also if it's acceptable by Parabola standards for package name to mention the blacklisted package.
Related issues
History
Updated by bill-auger about 2 years ago
- Priority changed from bug to broken
- Assignee set to oaken-source
- Tracker changed from Freedom issue to Packaging request
confirmed
$ sudo pacman -S firefox-extension-privacybadger
resolving dependencies...
warning: cannot resolve "firefox", a dependency of "firefox-extension-privacybadger"
:: The following package cannot be upgraded due to unresolvable dependencies:
firefox-extension-privacybadger
$ pacman -Sg firefox-addons
firefox-addons firefox-extension-privacybadger
seeing as this is in a group named 'firefox-addons' there will presumably be more add-ons added soon
the simplest solution is to make 'iceweasel' to provides('firefox') or else all packages added to this group are going to need to be blacklisted or re-packaged for no reason other than changing the package name
Updated by bill-auger about 1 year ago
- Related to Packaging request #1899: HTTPS Everywhere added
Updated by bill-auger about 1 year ago
- Related to Packaging request #2164: [iceweasel][iceweasel-addons] Provide /usr/lib/firefox symlink to drop iceweasel-specific extensions in favor of ones from Arch added