Package Details: librewolf-bin 125.0.3-1.1

Git Clone URL: https://aur.archlinux.org/librewolf-bin.git (read-only, click to copy)
Package Base: librewolf-bin
Description: Community-maintained fork of Firefox, focused on privacy, security and freedom.
Upstream URL: https://librewolf-community.gitlab.io/
Keywords: browser web
Licenses: GPL, MPL, LGPL
Conflicts: librewolf
Provides: librewolf
Submitter: lsf
Maintainer: lsf
Last Packager: lsf
Votes: 351
Popularity: 14.99
First Submitted: 2019-06-16 13:12 (UTC)
Last Updated: 2024-05-02 20:04 (UTC)

Dependencies (16)

Required by (23)

Sources (7)

Pinned Comments

lsf commented on 2021-11-10 12:14 (UTC) (edited on 2023-04-17 07:18 (UTC) by lsf)

https://wiki.archlinux.org/title/Arch_User_Repository#Acquire_a_PGP_public_key_if_needed

gpg --keyserver hkp://keyserver.ubuntu.com --search-keys 031F7104E932F7BD7416E7F6D2845E1305D6E801

/edit: starting with 112.0-1, the binaries are signed with the maintainers shared key, so gpg --keyserver hkp://keyserver.ubuntu.com --search-keys 662E3CDD6FE329002D0CA5BB40339DD82B12EF16 should do the trick instead. I've also signed the key with the previously used key, so you have at least some guarantee that it's not a malicious attack :)

Latest Comments

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 Next › Last »

lsf commented on 2021-04-05 20:34 (UTC)

Thanks for pointing that out – I must've skipped that point when it came to mentioning JAVA.

Anyway: it's not clear to me what exactly is meant by that. The whole phrase is: "Packages that use prebuilt deliverables, when the sources are available, must use the -bin suffix. An exception to this is with Java. The AUR should not contain the binary tarball created by makepkg, nor should it contain the filelist."

From how I understand it, it's more about things like adding the pkg.tar. to the AUR (as in commiting it to the AUR), and not about using a pkg.tar. from elsewhere as a source. So as long as it's a -bin package, everything should be alright.

Which would, to my mind, "make the most sense" – because why would this be any different than a binary packaged for anything else?; as long as I'm not pulling the pkg.tar. from the official upstream repos (or putting the pkg.tar. on the AUR which would fit better with the "should not contain the binary tarball.." part).

I might still be totally in the wrong here, but neither do I see what about my approach here is detrimental (except it being somewhat inelegant) to Arch / the AUR, nor am I certain it's meant the way you say.

So if you could help me out a bit further on that (by clarifying that it is indeed meant the way you say it is) or if you could provide me a somewhat more clearly phrased source / some statement somewhere, that would be great!

Again, not trying to be a pain here – just trying to see what's the best way to somehow get everyone happy on this ^^

FabioLolix commented on 2021-04-05 20:14 (UTC)

From https://wiki.archlinux.org/index.php/AUR_submission_guidelines#Rules_of_submission

"The AUR should not contain the binary tarball created by makepkg"

If you want to help users create a repository, make a pinned post about it in the librewolf AURweb page and get it listed in the list of unofficial Arch repos

lsf commented on 2021-04-05 20:05 (UTC) (edited on 2021-04-05 20:12 (UTC) by lsf)

That would be news to me – but I might have missed that, so could you be so kind as to tell me where it says that? (couldn't find it by quickly looking at the guidelines in the wiki).

If that would truly be a problem, I would remove the package – although I'd hope that this could be avoided; considering that the AUR is "the first place" people will probably look for a package that's not in the upstream repos. The alternative would be just relying on external repos (like https://privacyshark.zero-credibility.net/), but those would have to be "discovered" first, or by doing something even more inelegant/hacky like taking a non-arch-specific prebuilt version (debian?) and trying to coerce it into an Arch package – which would probably lead to a bin-release of lesser quality.

/edit

Oh well, I could also have the CI on the other end of all this additionally spit out a version that's just a plain old tar.zst of the contents that would normally go into the pkg.tar.xz, if all else failed. That way it would be "compliant" while still providing an easy to use/find bin-release of it via the AUR. Not trying to be a pain here – I just want it to be easy to use even for those not wanting to build from source.

FabioLolix commented on 2021-04-05 19:44 (UTC)

Hello, this kind of pkgbuild where the source is an already build Arch package are against submission rules

B28302 commented on 2021-04-05 18:00 (UTC)

@mwohah Yes, using Whonix Gateway. Now using Flatpak with success.

Gert-dev commented on 2021-04-05 15:21 (UTC)

@B28302 Are you using Tor by any chance?

I often encounter 403 errors when downloading LibreWolf from GitLab (some requests also get 403 errors on GitLab itself) when Tor is enabled as system-wide proxy in GNOME. (This is likely related to GitLab switching to CloudFlare a while ago, getting on GitLab using Tor has been hit and miss since then, due to their aggressive firewall policies.)

0000000000 commented on 2021-04-01 22:27 (UTC) (edited on 2021-04-01 22:31 (UTC) by 0000000000)

i dunno. I clicked the build button on the manjaro software manager for this (and it was this 100%) and firedragon got installed. After like 10 failed attempts at trying to install the non bin version of this and removing dependencies a couple times I wouldn't be surprised if something broke. I'll try installing this again to see what happens for science.

---edit--- I got this message this time. "The PGP key 031F7104E932F7BD7416E7F6D2845E1305D6E801 is needed to verify librewolf-bin source files. Trust ohfp repo key (Repository signing key for privacyshark repo) 1813007-ohfp@users.noreply.gitlab.com and import the PGP key ?" said sure, go for it mr puter. Seems to have installed.

lsf commented on 2021-04-01 16:36 (UTC)

It shouldn't. If that were the case, someone would've had to steal my hardware token (and passphrase) to sign a completely different binary with my keys.

What I'm saying is: I can only assume that something is very, very odd with your system if by installing this package you'd end up with firedragen ;) (eg. something messed up with binary names, $PATH or some .desktop-files?)

0000000000 commented on 2021-04-01 15:55 (UTC)

...why did this install firedragon?

lsf commented on 2021-02-18 07:26 (UTC) (edited on 2021-02-18 07:26 (UTC) by lsf)

@B28302

I can only assume that is an issue with your system or internet provider (?), the files can be reached from my end.

You can try to get them directly from https://gitlab.com/librewolf-community/browser/linux/-/releases/v85.0.2-2 or the CI job instead https://gitlab.com/librewolf-community/browser/arch/-/jobs/1030006580/artifacts/file/librewolf-85.0.2-2-x86_64.pkg.tar.zst, maybe you'll get a more helpful error in the browser?

  -> Downloading librewolf-85.0.2-2-x86_64.pkg.tar.zst...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 76.0M  100 76.0M    0     0  23.1M      0  0:00:03  0:00:03 --:--:-- 23.1M
  -> Downloading librewolf-85.0.2-2-x86_64.pkg.tar.zst.sig...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   119  100   119    0     0    268      0 --:--:-- --:--:-- --:--:--   268
  -> Downloading librewolf-85.0.2-2-aarch64.pkg.tar.zst...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 54.8M  100 54.8M    0     0  3005k      0  0:00:18  0:00:18 --:--:-- 6341k
  -> Downloading librewolf-85.0.2-2-aarch64.pkg.tar.zst.sig...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   119  100   119    0     0    254      0 --:--:-- --:--:-- --:--:--   254