Hm, must have messed it up somewhere – could have sworn it hat worked before.
I've just pushed a new version anyway, so I hope now the checksums are correct again :)
| 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) |
« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 Next › Last »
Hm, must have messed it up somewhere – could have sworn it hat worked before.
I've just pushed a new version anyway, so I hope now the checksums are correct again :)
Currently failing the sha256 checksum:
~% paru -S librewolf-bin
:: Resolving dependencies...
:: Calculating conflicts...
:: Calculating inner conflicts...
Repo (2) mozilla-common-1.4-6 startup-notification-0.12-7
Aur (1) librewolf-bin-85.0.1-1
:: Proceed to review? [Y/n]:
:: Downloading PKGBUILDs...
PKGBUILDs up to date
nothing new to review
:: Proceed with installation? [Y/n]:
resolving dependencies...
looking for conflicting packages...
Packages (2) mozilla-common-1.4-6 startup-notification-0.12-7
Total Installed Size: 0.06 MiB
:: Proceed with installation? [Y/n]
(2/2) checking keys in keyring
(2/2) checking package integrity
(2/2) loading package files
(2/2) checking for file conflicts
(2/2) checking available disk space
:: Processing package changes...
(1/2) installing mozilla-common
relogin or source /etc/profile.d/mozilla-common.sh
(2/2) installing startup-notification
fetching devel info...
==> Making package: librewolf-bin 85.0.1-1 (Mon 15 Feb 2021 05:14:06 PM CET)
==> Retrieving sources...
-> Found librewolf-85.0.1-1-x86_64.pkg.tar.zst
-> Found librewolf-85.0.1-1-x86_64.pkg.tar.zst.sig
==> Validating source_x86_64 files with sha256sums...
librewolf-85.0.1-1-x86_64.pkg.tar.zst ... FAILED
librewolf-85.0.1-1-x86_64.pkg.tar.zst.sig ... Skipped
==> ERROR: One or more files did not pass the validity check!
:: Packages failed to build: librewolf-bin-85.0.1-1
Trying to skip the checksums also did not work:
~% paru -S librewolf-bin --mflags "--skipchecksums"
:: Resolving dependencies...
:: Calculating conflicts...
:: Calculating inner conflicts...
Aur (1) librewolf-bin-85.0.1-1
:: Proceed to review? [Y/n]:
:: Downloading PKGBUILDs...
PKGBUILDs up to date
nothing new to review
:: Proceed with installation? [Y/n]:
fetching devel info...
==> Making package: librewolf-bin 85.0.1-1 (Mon 15 Feb 2021 05:39:11 PM CET)
==> Retrieving sources...
-> Found librewolf-85.0.1-1-x86_64.pkg.tar.zst
-> Found librewolf-85.0.1-1-x86_64.pkg.tar.zst.sig
==> WARNING: Skipping verification of source file checksums.
==> Verifying source file signatures with gpg...
librewolf-85.0.1-1-x86_64.pkg.tar.zst ... FAILED
==> ERROR: One or more PGP signatures could not be verified!
:: Packages failed to build: librewolf-bin-85.0.1-1
After trying to install it manually, I discover that it created to "pacman installables": librewolf-85.0.1-1-x86_64.pkg.tar.zst and librewolf-bin-85.0.1-1-x86_64.pkg.tar.zst.
librewolf-85.0.1-1-x86_64.pkg.tar.zst: failed at PGP key signaturelibrewolf-bin-85.0.1-1-x86_64.pkg.tar.zst: installs correctlyThanks lsf. It is working now :)
That's true – I've removed the second key for now, as mostly it's the first one that's used to sign the releases anyway.
Hello lsf. I read your previous comment, imported the keys, it still will not work.
:: PGP keys need importing: -> 9D7008F8DFCD21508174954A3740FE9FC5772203, required by: librewolf-bin ==> Import? [Y/n] Y :: Importing keys with gpg... gpg: keyserver receive failed: No data problem importing keys
I think now the package expects both keys to be there, but only one is there
"Standard practices" apply for verifying the signatures:
The key is available on sks-keyservers.net or keys.gnupg.net (at least).
You can manually download it and import it (eg: http://keys.gnupg.net/pks/lookup?op=get&search=0xD2845E1305D6E801), or get it with gpg: gpg --search-keys 031F7104E932F7BD7416E7F6D2845E1305D6E801 or gpg --recv-keys 031F7104E932F7BD7416E7F6D2845E1305D6E801. If you have set a different keyserver in your gnupg config, you can specify a keyserver directly by adding --keyserver url.to.some.keyserver, eg.: gpg --keyserver keys.gnupg.net --search-keys 031F7104E932F7BD7416E7F6D2845E1305D6E801 or gpg --keyserver keys.gnupg.net --recv-keys 031F7104E932F7BD7416E7F6D2845E1305D6E801.
If you absolutely do not care about signature verification, you can also skip it by adding --skippgpcheck when running makepkg, yay, paru etc.
==> ERROR: One or more PGP signatures could not be verified!
FYI, error verifying source file signatures with gpg (keys not imported). Installation aborts:
==> Verifying source file signatures with gpg...
librewolf-84.0.2-1-x86_64.pkg.tar.zst ... FAILED (unknown public key 2954CC8585E27A3F)
==> ERROR: One or more PGP signatures could not be verified!
:: PGP keys need importing: -> 031F7104E932F7BD7416E7F6D2845E1305D6E801, required by: librewolf-bin -> 9D7008F8DFCD21508174954A3740FE9FC5772203, required by: librewolf-bin ==> Import? [Y/n] Y :: Importing keys with gpg... gpg: keyserver receive failed: No name problem importing keys
@lsf thanks! That fixes the problem. For now I've timeboxed it; I might submit PR-s in the future, if that'll be needed
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 662E3CDD6FE329002D0CA5BB40339DD82B12EF16should 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.xztarballs 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) viagpg --refresh-keys 662E3CDD6FE329002D0CA5BB40339DD82B12EF16.