Package Details: librewolf 1:137.0.2_1-1

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: 170
Popularity: 12.18
First Submitted: 2019-06-14 18:41 (UTC)
Last Updated: 2025-04-16 17:19 (UTC)

Dependencies (62)

Sources (3)

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).

Latest Comments

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 33 Next › Last »

Bitals commented on 2022-08-14 12:52 (UTC)

@karolyi 103.0.2 still doesn't build for me with rust 1.63.0:

12:45:51  4:36.69    --> /home/builder/.cache/aurutils/sync/librewolf/src/firefox-103.0.2/third_party/rust/packed_simd_2/src/lib.rs:347:7
12:45:51  4:36.69     |
12:45:51  4:36.69 347 | crate mod llvm {
12:45:51  4:36.69     |       ^^^ expected one of `!` or `::`
12:45:51  4:36.71 error: could not compile `packed_simd_2` due to previous error
12:45:51  4:36.71 warning: build failed, waiting for other jobs to finish...
12:45:51  4:36.88 dom/serviceworkers
12:45:51  4:36.92 dom/serializers
12:45:52  4:37.30 dom/simpledb
12:45:52  4:37.44 dom/storage
12:45:52  4:37.45 dom/smil
12:45:54  4:39.40 dom/streams
12:45:54  4:39.53 make[4]: *** [/home/builder/.cache/aurutils/sync/librewolf/src/firefox-103.0.2/config/makefiles/rust.mk:430: force-cargo-library-build] Error 101
12:45:54  4:39.53 make[3]: *** [/home/builder/.cache/aurutils/sync/librewolf/src/firefox-103.0.2/config/recurse.mk:72: toolkit/library/rust/target] Error 2

ZhangHua commented on 2022-08-14 02:48 (UTC) (edited on 2022-08-14 12:18 (UTC) by ZhangHua)

Hello, I think you should add a LANG=C when calling pacman in Line 157 of PKGBUILD, because user's locale may not be English (like me) and grep Version may get nothing

karolyi commented on 2022-08-13 08:22 (UTC)

Can confirm it builds with that rust version. I'm on manjaro though so having that rust version is not such a big challenge.

103.0.1 didn't built at all, I've had a compiler error, as in the compiler (llvm) itself crashed. 103.0.2 seems to have fixed this.

lsf commented on 2022-08-12 09:16 (UTC)

That's probably due to rust having been updated just yesterday. You might give downgrading to 1:1.62.1-1 a try to get it built, until a fix surfaces somewhere.

lahwaacz commented on 2022-08-12 07:01 (UTC)

Version 103.0.2-1 does not build:

 5:11.64 error: expected one of `!` or `::`, found keyword `mod`
 5:11.64    --> /build/librewolf/src/firefox-103.0.2/third_party/rust/packed_simd_2/src/lib.rs:347:7
 5:11.64     |
 5:11.64 347 | crate mod llvm {
 5:11.64     |       ^^^ expected one of `!` or `::`
 5:11.64 error: could not compile `packed_simd_2` due to previous error
 5:11.97 make[4]: *** [/build/librewolf/src/firefox-103.0.2/config/makefiles/rust.mk:430: force-cargo-library-build] Error 101
 5:11.97 make[3]: *** [/build/librewolf/src/firefox-103.0.2/config/recurse.mk:72: toolkit/library/rust/target] Error 2
 5:11.97 make[3]: *** Waiting for unfinished jobs....

eclairevoyant commented on 2022-08-02 02:23 (UTC)

@nightly @SomeGuy016 The correct way to build this is in a chroot, as documented on the wiki: https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

This way it should never matter what version of psutil or whatever that you have installed on your system

lsf commented on 2022-08-01 16:49 (UTC) (edited on 2022-08-01 16:51 (UTC) by lsf)

Please don't flag this package as out of date for reasons other than it being out of date.

Recent example: Installation fails because of outdated pip version. "WARNING: You are using pip version 21.2.3; however, version 22.2.1 is available."

This is worthy of a comment (or an issue, but since it's just another instance of pip/py/env things, not so much), if at all (it's a warning – the failure cause is probably another thing altogether).

A reason for flagging it out of date would be if it was out of date.

Thanks!

/edit

One open issue regarding pip issues, for example, would be https://gitlab.com/librewolf-community/browser/arch/-/issues/89, with a potentially helpful note at https://gitlab.com/librewolf-community/browser/arch/-/issues/89#note_1045390006

SomeGuy016 commented on 2022-07-19 12:51 (UTC) (edited on 2022-07-19 12:54 (UTC) by SomeGuy016)

For those of you who want to build this with python virtual environments like @nobyte suggested, here's how I built it

First create the virtual environment (if you are building manually then I'd recommend running this in the same place as where you cloned the package, if you are using an AUR helper just run this anywhere in your home directory and delete it later)

python -m venv .venv

From there, activate the virtual environment

source .venv/bin/activate

Now you can install the proper version of psutil to the venv by running

pip install psutil==5.8.0

Then just continue building the package as you normally would. Once it is installed, run

deactivate

to exit your virtual environment

nightly commented on 2022-07-13 11:07 (UTC)

Can someone help me? Whenever I try to build the package I get this error. http://dpaste.com/G3BZYFJUY I have tried @nobyte's patch but it yields no change.

nobyte commented on 2022-07-06 09:07 (UTC) (edited on 2022-07-06 09:22 (UTC) by nobyte)

@franz

You could probably somehow solve this (in a clean way) by using a python virtual environment with the right package version of psutil, but I don't know how to do that.

But here's a (somewhat dirty) work around. Downgrade the python-psutil package to the required version:

sudo pacman -U https://archive.archlinux.org/packages/p/python-psutil/python-psutil-5.8.0-4-x86_64.pkg.tar.zst
  • Downgrade to the required version:
sudo downgrade python-psutil

  • Choose right version

  • Set whether to ingore updates for this package (both options have pros/cons so choose what suits you better)

  • I installed some other packages to satisfy 'pip check', but this is dependant upon your installed packages and might not even be relevant to the Librewolf build

pacman -S python-brotli
pacman -S python-pybcj
pacman -S python-cmd2
  • As far as I understood there are many cases in which 'pip check' will complain about python packages that are irrelevant for the build of Firefox/Librewolf, so if the check fails, it's totally unnecessary for the build to stop then. See here : https://bugs.gentoo.org/828604#c5 ... so there was some patch and apparently some code was removed to resolve this ... the code isn't there anymore in the current BUT STILL the pip check runs and complains about some packages ... so I grep'ed through the source for "pip check" and found src/firefox-102.0/python/mach/mach/site.py ... I made a patch to comment the code that raises the failed pip check to an exception ... you can insert the text below in a file called librewolf_mach_site.py_disable_pip-check.patch in your build dir (on my system it is /var/tmp/pamac-build-user/librewolf). The content of the file:
--- a/python/mach/mach/site.py
+++ a/python/mach/mach/site.py
@@ -1118,10 +1118,10 @@
         if check_result.returncode:
             subprocess.check_call(pip + ["list", "-v"], stdout=sys.stderr)
             print(check_result.stdout, file=sys.stderr)
-            raise Exception(
-                'According to "pip check", the current Python '
-                "environment has package-compatibility issues."
-            )
+            #raise Exception(
+            #    'According to "pip check", the current Python '
+            #    "environment has package-compatibility issues."
+            #)

         os.environ[
             f"MACH_SYSTEM_ASSERTED_COMPATIBLE_WITH_{virtualenv_name.upper()}_SITE"
  • Then you need to edit the PKGBUILD (in my case in /var/tmp/pamac-build-user/librewolf) so that it finds and applies the patch before build ...
  • Add the name of the patch file from the previous step at the end of the sources list
source=(""
        ...
        "librewolf_mach_site.py_disable_pip-check.patch")

  # apply patch to disable pip check
  patch -Np1 -i ../librewolf_mach_site.py_disable_pip-check.patch
  • Start new build ... there may still be a warning about pip check, but instead of stopping the build should then continue

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 33 Next › Last »