| 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: | GPL, MPL, LGPL |
| Submitter: | lsf |
| Maintainer: | lsf |
| Last Packager: | lsf |
| Votes: | 147 |
| Popularity: | 3.73 |
| First Submitted: | 2019-06-14 18:41 (UTC) |
| Last Updated: | 2025-01-26 21:06 (UTC) |
I was trying to build this AUR and I got the following error:
==> Verifying source file signatures with gpg...
firefox-98.0.source.tar.xz ... FAILED (unknown public key EBE41E90F6F12F6D)
==> ERROR: One or more PGP signatures could not be verified!
I had to run the following command to fix it:
gpg --keyserver hkps://keys.openpgp.org --recv-keys 14F26682D0916CDD81E37B6D61B7B526D98F0353
That's probably because the MR that was pointing to got merged (and doesn't exist anymore, as I was force pushing to update the MR / branch…).
If you can wait just a tiiiiny bit longer, I'll probably update the AUR packages today vor 98.0 – I've had some nasty issues getting the aarch64 build working, which is why things are delayed a bit.
If you're in a rush, you could probably just grab the latest PKGBUILD from https://gitlab.com/librewolf-community/browser/arch/-/blob/master/PKGBUILD and see if that works for you! :)
I'm trying to update librewolf after I installed it a few months ago with yay and I get this error now:
==> Validating source files with sha256sums...
firefox-97.0.2.source.tar.xz ... Passed
firefox-97.0.2.source.tar.xz.asc ... Skipped
librewolf.desktop ... Passed
source ... Skipped
settings ... Skipped
default192x192.png ... Passed
==> Verifying source file signatures with gpg...
firefox-97.0.2.source.tar.xz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
-> Extracting firefox-97.0.2.source.tar.xz with bsdtar
-> Creating working copy of source git repo...
Cloning into 'source'...
done.
fatal: reference is not a tree: 272f05d69b40953729bf05a1d7acda69f30804e6
==> ERROR: Failure while creating working copy of source git repo
Aborting...
Any ideas? Edit: @lsf: thank you, the issue has been resolved!
@prg If you use fewer cores/threads for your virtual machine, you can likely get away with less memory.
@Eile I have been using a VM with 14GB of RAM to regularly compile librewolf, but as of 97.0.2 the librewolf build process is using more memory than before and is getting OOM-killed during the build.
Perhaps something changed in the firefox build scripts in this most recent version that require more memory ?
Apologies, librewolf fails to build. I am not using a chroot, simply running makepkg -sCcr. Here is the log: https://gist.github.com/Orangian/01153fc924511ca7be4d181640c8f774
Any help would be much appreciated!
edit: Whoops! Appears to be my fault. The system is killing the compilation due to me running out of memory. 16 GiB is apparently not enough.
edit2: I have 14 GiB free at time of compile, should that be enough?
Ah, yeah – unfortunately, pgp verification in the chroot is a bit… complicated.
To skip it, you could just run makechrootpkg -c -r /chroot/path/wherever -- --skippgpcheck (assuming you run it with mackechrootpkg, with paru it would be something with --mflags, iirc, or maybe even "just" --skippgpcheck) – this will pass the option to the chrooted makepkg to skip it.
I’m trying to build librewolf in a clean chroot, but I’m getting the following error:
==> Validating source files with sha256sums...
firefox-96.0.3.source.tar.xz ... Passed
firefox-96.0.3.source.tar.xz.asc ... Skipped
librewolf.desktop ... Passed
common ... Skipped
settings ... Skipped
default192x192.png ... Passed
==> Verifying source file signatures with gpg...
firefox-96.0.3.source.tar.xz ... FAILED (unknown public key EBE41E90F6F12F6D)
==> ERROR: One or more PGP signatures could not be verified!
==> ERROR: Could not download sources.
Hm, that's really odd stuff.
It seems for some users just removing python-pip for the duration of the build might've done the trick, but in the end that's probably something that needs to be addressed upstream.
I'd recommend building in a clean chroot (as described in https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot or with paru, which supports chroot building directly) – that should avoid any kind of conflicts with anything installed on the base system.
Same issue. MACH_USE_SYSTEM_PYTHON is no help for me either.
This is probably be due to this change:
https://phabricator.services.mozilla.com/rMOZILLACENTRALca4d439114f34488f746c60ee022ebce1204552a
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).