| 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.59 |
| First Submitted: | 2019-06-14 18:41 (UTC) |
| Last Updated: | 2025-05-30 11:41 (UTC) |
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
At least one month I have this issue, export MACH_USE_SYSTEM_PYTHON=0 doesn't help at all
==> Starting build()...
Building instrumented browser...
psutil<=5.8.0,>=5.4.2: Installed with unexpected version "5.9.0"
Traceback (most recent call last):
File "/home/user/.cache/paru/clone/librewolf/src/firefox-96.0.2/./mach", line 126, in <module>
main(sys.argv[1:])
File "/home/user/.cache/paru/clone/librewolf/src/firefox-96.0.2/./mach", line 118, in main
mach = check_and_get_mach(os.path.dirname(os.path.realpath(__file__)))
File "/home/user/.cache/paru/clone/librewolf/src/firefox-96.0.2/./mach", line 105, in check_and_get_mach
return load_mach(dir_path, mach_path)
File "/home/user/.cache/paru/clone/librewolf/src/firefox-96.0.2/./mach", line 91, in load_mach
return mach_initialize.initialize(dir_path)
File "/home/user/.cache/paru/clone/librewolf/src/firefox-96.0.2/build/mach_initialize.py", line 219, in initialize
_activate_python_environment(
File "/home/user/.cache/paru/clone/librewolf/src/firefox-96.0.2/build/mach_initialize.py", line 172, in _activate_python_environment
mach_environment = MachSiteManager.from_environment(
File "/home/user/.cache/paru/clone/librewolf/src/firefox-96.0.2/python/mach/mach/site.py", line 259, in from_environment
if external_python.provides_any_package("mach", requirements)
File "/home/user/.cache/paru/clone/librewolf/src/firefox-96.0.2/python/mach/mach/site.py", line 800, in provides_any_package
raise Exception(
Exception: The Python packages associated with "/usr/bin/python3" aren't compatible with the "mach" virtualenv
==> ERROR: A failure occurred in build().
Aborting...
error: failed to build 'librewolf-96.0.2-1':
error: packages failed to build: librewolf-96.0.2-1So I updated the MACH_USE_SYSTEM_PYTHON flag to 0, but when building I get the exact same issue as I had before (with the only difference being the updated firefox version number 96.0.2).
I am not certain why this kind of errors only crops up now, but a quick workaround might just be to change line 222 in the PKGBUILD (https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=librewolf#n220) to export MACH_USE_SYSTEM_PYTHON=0. That should stop it from trying to use any system-wide packages/python completely.
Same issue here also
When building for 96 I no longer have the pip issue, but I now get the following once the build starts.
==> Starting build()...
Building instrumented browser...
psutil<=5.8.0,>=5.4.2: Installed with unexpected version "5.9.0"
Traceback (most recent call last):
File "/home/gin/.aur/librewolf/src/firefox-96.0/./mach", line 126, in <module>
main(sys.argv[1:])
File "/home/gin/.aur/librewolf/src/firefox-96.0/./mach", line 118, in main
mach = check_and_get_mach(os.path.dirname(os.path.realpath(__file__)))
File "/home/gin/.aur/librewolf/src/firefox-96.0/./mach", line 105, in check_and_get_mach
return load_mach(dir_path, mach_path)
File "/home/gin/.aur/librewolf/src/firefox-96.0/./mach", line 91, in load_mach
return mach_initialize.initialize(dir_path)
File "/home/gin/.aur/librewolf/src/firefox-96.0/build/mach_initialize.py", line 219, in initialize
_activate_python_environment(
File "/home/gin/.aur/librewolf/src/firefox-96.0/build/mach_initialize.py", line 172, in _activate_python_environment
mach_environment = MachSiteManager.from_environment(
File "/home/gin/.aur/librewolf/src/firefox-96.0/python/mach/mach/site.py", line 259, in from_environment
if external_python.provides_any_package("mach", requirements)
File "/home/gin/.aur/librewolf/src/firefox-96.0/python/mach/mach/site.py", line 800, in provides_any_package
raise Exception(
Exception: The Python packages associated with "/usr/bin/python3" aren't compatible with the "mach" virtualenv
==> ERROR: A failure occurred in build().
Aborting...
Any thoughts or suggestions? It really seems to me that the upgrade to python 3.10 is really hurting this build system, as I never had any issues building this before the upgrade.
@D1sturbed You can edit your past comment and fix the formatting...
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).