| 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: | 204 |
| Popularity: | 6.70 |
| First Submitted: | 2019-06-14 18:41 (UTC) |
| Last Updated: | 2026-01-17 23:07 (UTC) |
https://rpm.librewolf.net/pubkey.gpg was updated, new key 8A74EAAF89C17944 was added:
==> Verifying source file signatures with gpg...
librewolf-146.0.1-1.source.tar.gz ... FAILED (unknown public key 8A74EAAF89C17944)
Should probably update validpgpkeys.
Hello, I am getting this compile error
0:48.10 error: failed to build archive at `/home/derelbenkoenig/.cache/trizen/sources/librewolf/src/librewolf-146.0-2/obj-x86_64-pc-linux-gnu/x86_64-unknown-linux-gnu/release/deps/libcubeb_core-8154107cf508a4a9.rlib`: LLVM error: Unknown attribute kind (102) (Producer: 'LLVM21.1.6' Reader: 'LLVM 19.1.5-rust-1.84.1-stable')
0:48.11 warning: cubeb-core@0.30.1: Inherited flag "-fno-omit-frame-pointer" is not supported by the currently used CC
0:48.11 error: could not compile `cubeb-core` (lib) due to 1 previous error
and I'm not sure what to do about it.
"not supported by the currently used CC" makes it sound like maybe I need to update clang or gcc or something? never mind that's an unrelated warning I think
Hey,
there is a checksum error for librewolf-142.0.1-1.source.tar.gz:
==> Making package: librewolf 1:142.0.1_1-1 (Sat 30 Aug 2025 01:03:35 PM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading librewolf-142.0.1-1.source.tar.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 963M 100 963M 0 0 88.9M 0 0:00:10 0:00:10 --:--:-- 97.7M
-> Found librewolf.desktop
-> Found default192x192.png
==> Validating source files with sha256sums...
librewolf-142.0.1-1.source.tar.gz ... FAILED
librewolf.desktop ... Passed
default192x192.png ... Passed
==> ERROR: One or more files did not pass the validity check!
Fails to build for me on 0:04.67 ERROR: Wasm C compiler target CPU (x86_64) does not match --wasm CPU (wasm32)
@xiota thanks for your comment. I got it right, just asked about it wrong, :) If I wanted to try PGO with xvfb, then I need both variables set to true, and what I did was just that:
3 # run pgo build or not; with X(vfb) or wayland
4 : ${_build_profiled:=true}
5 : ${_build_profiled_xvfb:=true}
So all good, :)
@ToneyFox, PGO requires some sort of runtime environment to perform the [dynamic] profiling, see PGO. And those PGO depencies are chosen depending on:
if [[ "${_build_profiled}" == "true" ]]; then
if [[ "${_build_profiled_xvfb}" == "true" ]]; then
makedepends+=(
xorg-server-xvfb
)
else
makedepends+=(
weston
xorg-xwayland
wlheadless-run # aur/xwayland-run-git
)
fi
fi
I found the PKGBUILD very useful, but needs manual intervention if you don't want the default. I didn't want to profile on top of wayland, so I chose the xvfb variable to true to profile on top of x11 stuff. Both false is also valid and there's no additional make dependency for PGO.
Make dependencies are dependencies. XWayland is quite obviously not needed to build the package, not sure how anyone could believe it potentially is
xorg-xwayland is not a depends. It's a makedep that was required for profiling and not worth the time to test whether it's still strictly required.
Why does this depend on XWayland? That should be optional
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).