Package Details: librewolf-bin 1:150.0.3_1-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: MPL-2.0
Conflicts: librewolf
Provides: librewolf
Submitter: lsf
Maintainer: lsf
Last Packager: lsf
Votes: 626
Popularity: 24.26
First Submitted: 2019-06-16 13:12 (UTC)
Last Updated: 2026-05-13 07:44 (UTC)

Required by (39)

Sources (7)

Pinned Comments

lsf commented on 2021-11-10 12:14 (UTC) (edited on 2026-05-07 09:38 (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 :)

/edit: (2026-05-07): The upstream signing sub-key was rotated, and the .tar.xz tarballs will now be signed with a new subkey. The main key id (0x662E3CDD6FE329002D0CA5BB40339DD82B12EF16) remains unchanged though, so should you get an error during signature verification about a missing (sub)key, all that's required would be to refresh the key(s) via gpg --refresh-keys 662E3CDD6FE329002D0CA5BB40339DD82B12EF16.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 29 Next › Last »

syl commented on 2026-05-07 10:37 (UTC)

@lsf, if you need bit of help from an inexperienced hand as co-maintainer, please PM me.

Haunter commented on 2026-05-07 09:43 (UTC)

@lsf I see it now. Thank you

ninchuka commented on 2026-05-07 09:40 (UTC)

cheers jaycuse that got it working for me <3

lsf commented on 2026-05-07 09:37 (UTC)

@Haunter: oh, I can answer that: just hasn't been pushed there yet. Should happen in a few minutes :D

Haunter commented on 2026-05-07 09:36 (UTC) (edited on 2026-05-07 20:50 (UTC) by Haunter)

Forgive my paranoia, but if rel -2 is legitimate, then why doesn't it show up in the official git repo?

Edit: The git repo has since been updated to reflect the new rel: https://codeberg.org/librewolf/arch/src/branch/master/AUR/librewolf-bin/PKGBUILD

mEDI_S commented on 2026-05-07 06:54 (UTC)

u change ur pgp key?

  -> librewolf-150.0.1-1-linux-x86_64-package.tar.xz gefunden
  -> librewolf-150.0.1-1-linux-x86_64-package.tar.xz.sig gefunden
==> Überprüfe source Dateien mit sha256sums...
    source ... Erfolg
    default192x192.png ... Erfolg
    librewolf.desktop ... Erfolg
==> Überprüfe source_x86_64 Dateien mit sha256sums...
    librewolf-150.0.1-1-linux-x86_64-package.tar.xz ... Erfolg
    librewolf-150.0.1-1-linux-x86_64-package.tar.xz.sig ... Übersprungen
==> Überprüfe Signaturen der Quell-Dateien mit gpg...
    librewolf-150.0.1-1-linux-x86_64-package.tar.xz ... FEHLGESCHLAGEN (Unbekannter öffentlicher Schlüssel 915585A1C36690B1)
==> FEHLER: Eine oder mehrere PGP-Signaturen konnten nicht überprüft werden!
 -> Fehler beim Erstellen: librewolf-bin-exit status 1

jaycuse commented on 2026-05-07 00:09 (UTC) (edited on 2026-05-07 00:10 (UTC) by jaycuse)

@ninchuka

I had same error pop up. Solved it by clearing the cache for my package manager.

I use yay so what fixed it for me was: rm -rf ~/.cache/yay/librewolf-bin

ninchuka commented on 2026-05-06 22:25 (UTC)

I've tried running the gpg command from lsf but I still get a similar error to jericho

 -> error fetching librewolf-bin: error: The following untracked working tree files would be overwritten by merge:
        librewolf-150.0.1-1-linux-x86_64-package.tar.xz.sig
Please move or remove them before you merge.
Aborting
         context: exit status 1

from yay

syl commented on 2026-05-06 17:06 (UTC)

@Jericho just read the comment from the package maintainer, just below.