| Git Clone URL: | https://aur.archlinux.org/librewolf.git (read-only, click to copy) |
|---|---|
| Package Base: | librewolf |
| Description: | Community-maintained fork of Firefox, focused on privacy, security and freedom. |
| Upstream URL: | https://librewolf.net/ |
| Keywords: | browser web |
| Licenses: | MPL-2.0 |
| Submitter: | lsf |
| Maintainer: | lsf |
| Last Packager: | lsf |
| Votes: | 175 |
| Popularity: | 8.77 |
| First Submitted: | 2019-06-14 18:41 (UTC) |
| Last Updated: | 2025-05-30 11:41 (UTC) |
@odinvex,
that is an error on your end. I build this package for myself every time (since I use the allow_dark_preference_with_rfp.patch), and aside from the recent build error that happened to everyone, it builds just fine.
Your best bet is to try and see if executing the same command as the PKGBUILD does, fails in a shell, and if yes, why.
No, if you use a helper you're on your own. We can only help if you use makepkg on Arch Linux (not some other distro). Please check the rules of the AUR.
pamac is also categorically broken, you'd better use a helper that at least supports clean chroots like paru or aurutils (read the man pages to learn how to set up a chroot with them).
@eclairevoyant, Of course someone uses an AUR helper to use the AUR...since AURs are not part of Arch's official support. pamac, in this case. I've managed to get it working despite the issues, keeping a script I threw together for future installs.
@OdinVex Well let's see, you're not using Arch (unsupported) and you're probably using an AUR helper (unsupported) hence this is not the place to get support.
Edit: also, 4360FE2109C49763186F8E21EBE41E90F6F12F6D is a subkey and should have been imported automatically when you import the key mentioned in this PKGBUILD:
$ gpg --list-keys --keyid-format LONG --with-subkey-fingerprints 14F26682D0916CDD81E37B6D61B7B526D98F0353
pub rsa4096/61B7B526D98F0353 2015-07-17 [SC]
14F26682D0916CDD81E37B6D61B7B526D98F0353
uid [ unknown] Mozilla Software Releases <release@mozilla.com>
sub rsa4096/EBE41E90F6F12F6D 2021-05-17 [S] [expires: 2023-05-17]
4360FE2109C49763186F8E21EBE41E90F6F12F6D
So you didn't need to chase down some trunk builds. You also don't need to trust the key, as you can see the key is still marked unknown trust for me. Probably something is broken with your AUR helper so you should use makepkg or makechrootpkg.
Every month I try to install this on a new Manjaro install, and it has never worked. My comments keep getting removed, despite the fact that I keep bitching about the same error(s). PGP, despite import, despite commenting-out, still fails.
Verifying source file signatures with gpg... firefox-109.0.1.source.tar.xz ... cat: write error: Broken pipe
Edit: Finally seems like I managed to get around the crap by removing all pgp-key related stuff (all were imported, but all failed anyway with that broken pipe) and removed .asc reliances (and the SHA256 SKIP entry relevant).
Edit: The new Mozilla key (nowhere mentioned, included, or trusted) needed to be manually marked as Trusted. All imported, but none trusted by default. Found the key in the trunk builds. 4360FE2109C49763186F8E21EBE41E90F6F12F6D
I've just compiled Librewolf on my Manjaro successfully. I still need to compile it for myself because I keep using the ${_patches_dir}/removed-patches/allow_dark_preference_with_rfp.patch.
With the latest update, it seems to compile just fine.
I've just pushed an update (intentionally without bumping pkgrel) that should hopefully fix this.
That's good to know. Albeit odd.
(I had modified the patch to get the aarch64 build to be possible with webrtc, and the code change should be absolutely irrelevant for non-aarch64 builds. Doesn't seem to be the case though, so I'll have to use different patches for the different architectures here, instead of one for both, it seems. I'll address that asap.)
Thanks!
Got this to build by syncing 0001-libwebrtc-screen-cast-sync.patch update from firefox package https://archlinux.org/packages/extra/x86_64/firefox/
Maybe the GCC/Clang updates that recently came out?
Pinned Comments
lsf commented on 2025-01-01 21:28 (UTC)
Please refrain from abusing the flagging of a package as out of date for build issues. This is not what it is supposed to be used for.
I automatically get notified of comments to this package. I do not need to be notified of whatever build problems occur (whether they are an individual's problems or the actual package's problems) twice, and not via flagging it out of date.
Issues with this package can also be reported at https://codeberg.org/librewolf/issues/issues (as it is also maintained there, at https://codeberg.org/librewolf/arch, too).