Package Details: firefox-clearurls 1.26.1-1

Git Clone URL: (read-only, click to copy)
Package Base: firefox-clearurls
Description: Remove tracking elements from URL's to protect privacy while browsing.
Upstream URL:
Keywords: addon clearurl clearurls extension firefox firefox-addon privacy
Licenses: LGPL3
Groups: firefox-addons
Submitter: arojas
Maintainer: jeois (ryanbarillos)
Last Packager: ryanbarillos
Votes: 5
Popularity: 0.22
First Submitted: 2022-04-01 17:17 (UTC)
Last Updated: 2024-04-23 22:42 (UTC)

Dependencies (0)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

ryanbarillos commented on 2024-04-23 22:44 (UTC)


Now extension is updated to v1.26.1!

ryanbarillos commented on 2024-04-23 22:15 (UTC)

Been busy, but I'll get this done in a bit.

jeois commented on 2024-04-15 07:40 (UTC)

I agree that the source doesn't really matter as long as it gets done. Besides some minor reservations about unannounced versions and checksums, I was going to implement a method like you described. I only used the source method as a legacy from the previous maintainer and never figured out procedural retrieval from Mozilla's site instead. Thanks for the info.

Ryan, please go ahead and make the changes. Since I'm not using my Arch machine at the moment, I won't be able to test it for a while, but I trust it'll work just as well as firefox-blocktube. Thanks again.

ryanbarillos commented on 2024-04-15 06:14 (UTC)

Currently, I'm considering just using a method Firefox employs in its policy-templates guide: Pulling the latest version directly from the site

As seen here:

Been doing this on firefox-blocktube (an AUR package I maintain), and I'd like to know if this is fine instead of the route of compiling?

At the end of the day, the goal is to enforce this extension system-wide across all Firefox browsers, and neither a binary install from the website or a source-code compilation should affect that.

jeois commented on 2024-03-10 23:10 (UTC)

Yeah, I tried to update again, and it's still weird:

Both the plugin and the source for 1.26.1 on github are 404 missing. Meanwhile, the latest release on gitlab seems to be 1.23.1. Please read my last 3 comments to understand why this is an issue.

In the meantime, I've reverted this package to 1.23.1 because at least we're able to retrieve that version's source release. Hopefully, @ryanbarillos or someone can take over and fix this. Otherwise, comment here or message me if/when upstream release links work again.

jeois commented on 2024-03-10 21:37 (UTC) (edited on 2024-03-11 06:12 (UTC) by jeois)

So upstream did finally update the github release about a month after I last checked, but nobody commented telling me, and it wasn't mentioned in the orphan request either. It's true that I haven't really updated in over a year, but it wasn't due to lack of trying in the beginning.

Regardless, I'll hand it over to you, @ryanbarillos, since you made the request. I've made you a maintainer, and I'll disown the package entry if you update, and you'll become the sole maintainer.

jeois commented on 2023-10-02 05:12 (UTC)

I've known this has been out-of-date for a quite a long time, but unfortunately, the issue with the source versions I described has STILL not been resolved (i.e. no new releases on github or gitlab). There should be a way to build from source; but tbh, I can't be bothered due to the versioning issue (If we get the current master branch files from gitlab, what version is it when there's no release number? Moreover, this isn't a -git or -dev package, so I don't think live source updates are appropriate.)

I never actually agreed to maintain this, and I only updated because the source format fit the previous maintainer's PKGBUILD, making it simple. Nobody helped me with links or suggestions for 9 months. So now, even I have resorted to using Mozilla's Add-On site instead. If anyone wants to fix/update this package, then I'll gladly hand it off to you. Or, if you can convince the upstream project dev(s) to make a git release like before, then I'll start updating again.

jeois commented on 2023-01-09 17:31 (UTC)

The devs are making maintaining this package difficult. The Mozilla add-ons site has the newer version 1.26.0, and its source was on github for several months, but for some reason, they removed that release. So now, the only package available on github and gitlab is the older 1.23.1 (which wasn't mirrored well, as one git would have a release before the other for quite a while).

They might not realize that we rely on the releases here on the AUR. They probably assume fiddling with releases doesn't matter since they assume everyone gets the add-on from Mozilla's site. So, I'm stuck with a dilemma: I can revert this AUR entry to 1.23.1 matching the sources from the previous maintainer, OR I can try to pull the add-on binary indirectly from Mozilla (btw, if anyone knows of an easy way to get the link, please let me know).

I feel like as soon as I revert the version, they'll move the project to another host or come out with another release only to Mozilla. Please contact the upstream project if you want this consistent on the AUR. I can't figure out what they're doing with the versions and which source repository actually has the latest release.

jeois commented on 2022-12-28 01:07 (UTC)

@morealaz : Thanks for telling me. The source package file changed without any version bumps. It's been fixed now.

morealaz commented on 2022-12-23 07:02 (UTC)

@jeois : please fix checksum