Package Details: librewolf 130.0.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: GPL, MPL, LGPL
Submitter: lsf
Maintainer: lsf
Last Packager: lsf
Votes: 136
Popularity: 5.06
First Submitted: 2019-06-14 18:41 (UTC)
Last Updated: 2024-09-21 16:57 (UTC)

Dependencies (58)

Sources (3)

Latest Comments

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

ginnokami commented on 2021-12-22 11:41 (UTC) (edited on 2021-12-22 11:43 (UTC) by ginnokami)

Is anyone else having an issue compiling due to pip check having missing/updated/ dependencies? Running pip check will list some "missing or too updated packages" though all the actual programs run fine, and reinstalling the packages doesn't make the issue go away.

Exception: According to "pip check", the current Python environment has package-compatibility issues.
pip check
qmk 1.0.0 requires qmk-dotty-dict, which is not installed.
dotty-dict 1.3.0 requires setuptools-scm, which is not installed.
electrum 4.1.5 has requirement dnspython<2.1,>=2.0, but you have dnspython 2.1.0.
electrum 4.1.5 has requirement qdarkstyle<2.9, but you have qdarkstyle 3.0.2.

HurricanePootis commented on 2021-12-18 05:33 (UTC)

I think because of the wayland 1.20 update, projects have to update their code for new wayland release

dr460nf1r3 commented on 2021-12-17 06:18 (UTC)

Currently this patch is required for compiling FF95 :)

lahwaacz commented on 2021-12-17 06:07 (UTC) (edited on 2021-12-17 06:09 (UTC) by lahwaacz)

Building 95.0-1 in a clean chroot (with aurutils) just failed for me:

18:37.69 /usr/bin/ld: /usr/bin/ld: DWARF error: could not find variable specification at offset 4c
18:37.69 /usr/bin/ld: DWARF error: could not find variable specification at offset 733ea
18:37.70 /build/librewolf/src/firefox-95.0/obj/toolkit/library/build/../../../gfx/gl/Unified_cpp_gfx_gl0.o: in function `wl_surface_destroy(wl_surface*)':
18:37.70 /usr/include/wayland-client-protocol.h:3672: undefined reference to `wl_proxy_marshal_flags'
18:37.70 /usr/bin/ld: /usr/include/wayland-client-protocol.h:3672: undefined reference to `wl_proxy_marshal_flags'
18:37.70 /usr/bin/ld: /build/librewolf/src/firefox-95.0/obj/toolkit/library/build/../../../gfx/gl/Unified_cpp_gfx_gl0.o: in function `wl_compositor_create_surface(wl_compositor*)':
18:37.70 /usr/include/wayland-client-protocol.h:1291: undefined reference to `wl_proxy_marshal_flags'
18:38.63 /usr/bin/ld: /usr/bin/ld: DWARF error: could not find variable specification at offset 10b
18:38.63 /usr/bin/ld: DWARF error: could not find variable specification at offset 7aa
18:38.63 /usr/bin/ld: DWARF error: could not find variable specification at offset cb0
18:38.63 /usr/bin/ld: DWARF error: could not find variable specification at offset 1ab3
18:38.63 /usr/bin/ld: DWARF error: could not find variable specification at offset 1e65
18:38.63 /usr/bin/ld: DWARF error: could not find variable specification at offset 206e
18:38.63 /usr/bin/ld: DWARF error: could not find variable specification at offset 54da0
18:38.63 /usr/bin/ld: DWARF error: could not find variable specification at offset 54ddd
18:38.63 /usr/bin/ld: DWARF error: could not find variable specification at offset 55203
18:38.63 /usr/bin/ld: DWARF error: could not find variable specification at offset 55256
18:38.63 /usr/bin/ld: DWARF error: could not find variable specification at offset 55292
18:38.63 /usr/bin/ld: DWARF error: could not find variable specification at offset 552ce
18:38.63 /usr/bin/ld: DWARF error: could not find variable specification at offset 5530a
18:38.64 /build/librewolf/src/firefox-95.0/obj/toolkit/library/build/../../../widget/gtk/Unified_cpp_widget_gtk0.o: in function `wl_display_get_registry(wl_display*)':
18:38.64 /usr/include/wayland-client-protocol.h:1062: undefined reference to `wl_proxy_marshal_flags'
18:38.64 /usr/bin/ld: /build/librewolf/src/firefox-95.0/obj/toolkit/library/build/../../../widget/gtk/Unified_cpp_widget_gtk0.o: in function `wl_buffer_destroy(wl_buffer*)':
18:38.64 /usr/include/wayland-client-protocol.h:2017: undefined reference to `wl_proxy_marshal_flags'
18:38.64 /usr/bin/ld: /build/librewolf/src/firefox-95.0/obj/toolkit/library/build/../../../widget/gtk/Unified_cpp_widget_gtk0.o:/usr/include/wayland-client-protocol.h:2017: more undefined references to `wl_proxy_marshal_flags' follow
18:45.84 clang-13: error: linker command failed with exit code 1 (use -v to see invocation)
18:45.85 make[4]: *** [/build/librewolf/src/firefox-95.0/config/rules.mk:531: libxul.so] Error 1
18:45.85 make[3]: *** [/build/librewolf/src/firefox-95.0/config/recurse.mk:72: toolkit/library/build/target] Error 2
18:45.85 make[2]: *** [/build/librewolf/src/firefox-95.0/config/recurse.mk:34: compile] Error 2
18:45.85 make[1]: *** [/build/librewolf/src/firefox-95.0/config/rules.mk:352: default] Error 2
18:45.85 make: *** [client.mk:63: build] Error 2
18:45.87 152 compiler warnings present.
 Config object not found by mach.
Configure complete!
Be sure to run |mach build| to pick up any changes
==> ERROR: A failure occurred in build().
    Aborting...

Looks like the same issue @andreas_baumann has...

lsf commented on 2021-12-16 23:15 (UTC)

@karolyi: you'll probably have to build it yourself, yep in the future, yep – the patch is still available over at https://gitlab.com/librewolf-community/browser/common/-/blob/master/patches/allow_dark_preference_with_rfp.patch and is probably relatively simple to maintain: it's only a few tiny changes in the code, and as you can see in the repo there wasn't any need to change it in the past few months at all.

@andreas_baumann: no idea what's going on there – I'd assume it's something with your build environment (although I have no idea what exactly it might be – sorry about that). Things seemed to work fine in the clean dockerized (Arch) build env (https://gitlab.com/librewolf-community/browser/arch/-/jobs/1875446573), which I can always use as a cop-out and a "well it works for me" ;)

karolyi commented on 2021-12-16 21:40 (UTC)

Hey,

I'd like to have the allow_dark_preference_with_rfp.patch back. Is there a way to get it back, or do I need to fork this package and adjust it manually?

andreas_baumann commented on 2021-12-16 07:52 (UTC) (edited on 2021-12-16 09:39 (UTC) by andreas_baumann)

47:06.71     Finished release [optimized] target(s) in 43m 22s
47:20.15 toolkit/library/build/libxul.so
59:02.38 /usr/bin/ld: /usr/bin/ld: DWARF error: could not find variable specification at offset 4c
59:03.14 /usr/bin/ld: DWARF error: could not find variable specification at offset 733ea
59:03.14 /build/librewolf/src/firefox-95.0/obj/toolkit/library/build/../../../gfx/gl/Unified_cpp_gfx_gl0.o: in function `wl_surface_destroy(wl_surface*)':
59:03.14 /usr/include/wayland-client-protocol.h:3672: undefined reference to `wl_proxy_marshal_flags'
59:03.14 /usr/bin/ld: /usr/include/wayland-client-protocol.h:3672: undefined reference to `wl_proxy_marshal_flags'
59:03.14 /usr/bin/ld: /build/librewolf/src/firefox-95.0/obj/toolkit/library/build/../../../gfx/gl/Unified_cpp_gfx_gl0.o: in function `wl_compositor_create_surface(wl_compositor*)':
59:03.14 /usr/include/wayland-client-protocol.h:1291: undefined reference to `wl_proxy_marshal_flags'
59:52.25 /usr/bin/ld: /usr/bin/ld: DWARF error: could not find variable specification at offset 10b
59:52.25 /usr/bin/ld: DWARF error: could not find variable specification at offset 7aa
59:52.25 /usr/bin/ld: DWARF error: could not find variable specification at offset cb0
59:52.25 /usr/bin/ld: DWARF error: could not find variable specification at offset 1ab3
59:52.25 /usr/bin/ld: DWARF error: could not find variable specification at offset 1e65
59:52.25 /usr/bin/ld: DWARF error: could not find variable specification at offset 206e
59:52.25 /usr/bin/ld: DWARF error: could not find variable specification at offset 54da0
59:52.25 /usr/bin/ld: DWARF error: could not find variable specification at offset 54ddd
59:52.25 /usr/bin/ld: DWARF error: could not find variable specification at offset 55203
59:52.25 /usr/bin/ld: DWARF error: could not find variable specification at offset 55256
59:52.25 /usr/bin/ld: DWARF error: could not find variable specification at offset 55292
59:52.25 /usr/bin/ld: DWARF error: could not find variable specification at offset 552ce
59:52.25 /usr/bin/ld: DWARF error: could not find variable specification at offset 5530a
59:52.26 /build/librewolf/src/firefox-95.0/obj/toolkit/library/build/../../../widget/gtk/Unified_cpp_widget_gtk0.o: in function `wl_display_get_registry(wl_display*)':
59:52.66 /usr/include/wayland-client-protocol.h:1062: undefined reference to `wl_proxy_marshal_flags'
59:52.67 /usr/bin/ld: /build/librewolf/src/firefox-95.0/obj/toolkit/library/build/../../../widget/gtk/Unified_cpp_widget_gtk0.o: in function `wl_buffer_destroy(wl_buffer*)':
59:52.67 /usr/include/wayland-client-protocol.h:2017: undefined reference to `wl_proxy_marshal_flags'
59:52.67 /usr/bin/ld: /build/librewolf/src/firefox-95.0/obj/toolkit/library/build/../../../widget/gtk/Unified_cpp_widget_gtk0.o:/usr/include/wayland-client-protocol.h:2017: more undefined references to `wl_proxy_marshal_flags' follow
64:27.13 clang-13: error: linker command failed with exit code 1 (use -v to see invocation)
64:27.44 make[4]: *** [/build/librewolf/src/firefox-95.0/config/rules.mk:531: libxul.so] Error 1
64:27.44 make[3]: *** [/build/librewolf/src/firefox-95.0/config/recurse.mk:72: toolkit/library/build/target] Error 2
64:27.44 make[2]: *** [/build/librewolf/src/firefox-95.0/config/recurse.mk:34: compile] Error 2
64:27.44 make[1]: *** [/build/librewolf/src/firefox-95.0/config/rules.mk:352: default] Error 2
64:27.44 make: *** [client.mk:63: build] Error 2
64:27.44 152 compiler warnings present.

I suspect it's caused by mach buildsymbols, trying right now..

No success, there seems to be a messup in wayland or in the toolchain..

lsf commented on 2021-12-15 19:33 (UTC)

@neko-san: sorry for still not having added your changes to the PKGBUILD… I barely got the regular release done with quite a few days delay this time /o\

…I hope that will improve soon – I'll get to it! ^^

=> python-pip shouldn't be required as a dependency, though – I build the official releases not in a chroot, but in a freshly spun up docker container (https://gitlab.com/librewolf-community/browser/arch/-/jobs/1875446573 for the current one), so something like that should fail in there as well, I think.

Neko-san commented on 2021-12-12 09:21 (UTC) (edited on 2021-12-12 23:05 (UTC) by Neko-san)

~~And now, for some reason I don't understand, what I said still works but it doesn't work inside of a chroot (with Paru) for some reason I can't understand~~

One would think the opposite would make it build but no, somehow

EDIT: Seems it was because python-pip is a dependency now

Neko-san commented on 2021-11-22 18:14 (UTC) (edited on 2021-11-22 18:16 (UTC) by Neko-san)

1) options+=(!lto) - this makes sure that any user's global lto pacman/makepkg flag is overriden to stay off; this will throw errors if not done and the global is on

2) add ac_add_options --enable-linker=lld before the "instrumental build"; this is what was preventing compilation for me in the first place

3) uncomment:

  CFLAGS="${CFLAGS/-fno-plt/}"
  CXXFLAGS="${CXXFLAGS/-fno-plt/}"

because the builds will throw errors if they're not uncommented