Package Details: librewolf-bin 1:138.0.1_2-1

Git Clone URL: https://aur.archlinux.org/librewolf-bin.git (read-only, click to copy)
Package Base: librewolf-bin
Description: Community-maintained fork of Firefox, focused on privacy, security and freedom.
Upstream URL: https://librewolf.net/
Keywords: browser web
Licenses: GPL, MPL, LGPL
Conflicts: librewolf
Provides: librewolf
Submitter: lsf
Maintainer: lsf
Last Packager: lsf
Votes: 482
Popularity: 27.79
First Submitted: 2019-06-16 13:12 (UTC)
Last Updated: 2025-05-04 08:41 (UTC)

Dependencies (16)

Required by (34)

Sources (7)

Pinned Comments

lsf commented on 2021-11-10 12:14 (UTC) (edited on 2023-04-17 07:18 (UTC) by lsf)

https://wiki.archlinux.org/title/Arch_User_Repository#Acquire_a_PGP_public_key_if_needed

gpg --keyserver hkp://keyserver.ubuntu.com --search-keys 031F7104E932F7BD7416E7F6D2845E1305D6E801

/edit: starting with 112.0-1, the binaries are signed with the maintainers shared key, so gpg --keyserver hkp://keyserver.ubuntu.com --search-keys 662E3CDD6FE329002D0CA5BB40339DD82B12EF16 should do the trick instead. I've also signed the key with the previously used key, so you have at least some guarantee that it's not a malicious attack :)

Latest Comments

1 2 3 4 5 6 .. 22 Next › Last »

LokiNaBoki commented on 2025-05-03 08:26 (UTC)

When the package is updated the information about usr/lib/librewolf/librewolf.cfg.pacnew is always printed, even though it usually is not created. Could this message be put behind a if [[ -f '/usr/lib/librewolf/librewolf.cfg.pacnew' ]]?

Serial commented on 2025-04-21 00:42 (UTC)

librewolf-bin stopped opening after update and when trying to reinstall the following error message appears:

libfakeroot internal error: payload not recognized!

Errors occurred and therefore no packages were updated. -> error installing: [/home/edson/.cache/yay/librewolf-bin/librewolf-bin-1:137.0.2_1-1-x86_64.pkg.tar.zst /home/edson/.cache/yay/librewolf-bin/librewolf-bin-debug-1:137.0.2_1-1-x86_64.pkg.tar.zst] - exit status 1

marbens commented on 2025-03-21 01:36 (UTC)

@zlima12 librewolf/arch#18

zlima12 commented on 2025-03-21 00:25 (UTC)

The upstream URL should be updated to https://librewolf.net.

spsf64 commented on 2025-03-19 16:22 (UTC)

@marbens @karolyi, my bad, it is working fine, my shortcut was pointing to the old appimage I was testing. Will delete my comment...

karolyi commented on 2025-03-19 15:58 (UTC)

@spsf64, it works on my machine™

zlima12 commented on 2025-03-15 18:37 (UTC) (edited on 2025-03-15 18:38 (UTC) by zlima12)

@marbens yes, that would not have been that big of a deal considering the upstream release cadence. epoch bumps are only supposed to be used for major versioning breakage (e.g. 5.7.2 gets reset to 1.0.0). Really, I think that it should get reset to zero/undefined in the case of this package, but as mentioned before that would require manual intervention from users that have updated to epoch 1.

marbens commented on 2025-03-15 07:54 (UTC) (edited on 2025-03-15 07:58 (UTC) by marbens)

@zlima12 How else would we have solved the problem? Skip 136.0-2?

1 2 3 4 5 6 .. 22 Next › Last »