| 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.08 |
| First Submitted: | 2019-06-14 18:41 (UTC) |
| Last Updated: | 2025-05-30 11:41 (UTC) |
I suggest removing this line:
export MACH_USE_SYSTEM_PYTHON=1
(line 248)
This package will not compile (for me) otherwise, even in a chroot, because of pip errors (see whynothugo's problem).
Setting the 1 to 0 does not help btw, as the existence of the variable is checked. not the value.
Sorry, didn't clarify, this is on aarch64, on archlinuxarm/asahi-linux.
Running in a clean chroot (with paru -S --chroot) yields this:
Traceback (most recent call last):
File "/home/hugo/.cache/paru/clone/librewolf/src/firefox-98.0.1/./mach", line 96, in <module>
main(sys.argv[1:])
File "/home/hugo/.cache/paru/clone/librewolf/src/firefox-98.0.1/./mach", line 88, in main
mach = check_and_get_mach(os.path.dirname(os.path.realpath(__file__)))
File "/home/hugo/.cache/paru/clone/librewolf/src/firefox-98.0.1/./mach", line 35, in check_and_get_mach
return load_mach(dir_path, mach_path)
File "/home/hugo/.cache/paru/clone/librewolf/src/firefox-98.0.1/./mach", line 21, in load_mach
return mach_initialize.initialize(dir_path)
File "/home/hugo/.cache/paru/clone/librewolf/src/firefox-98.0.1/build/mach_initialize.py", line 160, in initialize
_activate_python_environment(
File "/home/hugo/.cache/paru/clone/librewolf/src/firefox-98.0.1/build/mach_initialize.py", line 99, in _activate_python_environment
mach_environment.activate()
File "/home/hugo/.cache/paru/clone/librewolf/src/firefox-98.0.1/python/mach/mach/site.py", line 333, in activate
self.ensure()
File "/home/hugo/.cache/paru/clone/librewolf/src/firefox-98.0.1/python/mach/mach/site.py", line 310, in ensure
up_to_date = self.up_to_date()
File "/home/hugo/.cache/paru/clone/librewolf/src/firefox-98.0.1/python/mach/mach/site.py", line 297, in up_to_date
_assert_pip_check(self._topsrcdir, pthfile_lines, "mach")
File "/home/hugo/.cache/paru/clone/librewolf/src/firefox-98.0.1/python/mach/mach/site.py", line 1060, in _assert_pip_check
raise Exception(
Exception: According to "pip check", the current Python environment has package-compatibility issues.
==> ERROR: A failure occurred in build().
Aborting...
error: failed to build 'librewolf-98.0.1-1':
error: packages failed to build: librewolf-98.0.1-1
Removing python-pip is tricky because it's a transitive dependency.
I was then getting this error:
Exception: The Python packages associated with "/usr/bin/python3" aren't compatible with the "mach" virtualenv
and used lsf's suggestion of removing python-pip for the duration of the build and it appeared to have worked but I am now getting this error:
patching file widget/moz.build
The next patch would create the file widget/nsINativeMenuService.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file widget/nsWidgetsCID.h
==> ERROR: A failure occurred in prepare().
Aborting...
I will now try to build it in a clean chroot environment, instead..
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?
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).