Successfully launched gpg --recv-keys 9AD8FC4162D7937CF64F972E1889D5F0E0636F49 and gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 9AD8FC4162D7937CF64F972E1889D5F0E0636F49 to import the key. Still getting "Verifying source file signatures with gpg... units-2.22.tar.gz ... cat: write error: Broken pipe"
Search Criteria
Package Details: units 2.24-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/units.git (read-only, click to copy) |
---|---|
Package Base: | units |
Description: | converts between different units |
Upstream URL: | https://www.gnu.org/software/units/units.html |
Keywords: | calculator conversion units |
Licenses: | GPL-3.0-or-later |
Submitter: | arojas |
Maintainer: | tarball |
Last Packager: | tarball |
Votes: | 43 |
Popularity: | 3.19 |
First Submitted: | 2023-04-01 17:48 (UTC) |
Last Updated: | 2024-11-28 14:57 (UTC) |
Dependencies (5)
- readline (readline-gitAUR)
- python-requests (make)
- python-unidecode (make)
- python-requests (optional) – for live currency rates
- python-unidecode (optional) – for live currency rates
Required by (2)
Sources (4)
Latest Comments
« First ‹ Previous 1 2
Mozai commented on 2023-05-24 20:01 (UTC)
cbb commented on 2023-04-07 15:22 (UTC)
I tried fetching the key with gpg --recv-keys
, which produces the following message:
gpg: key E0636F49: no user ID
gpg: Total number processed: 1
Running yay
then fails in the same way as before, seemingly because the key wasn't imported properly for the same reason as described here.
Running the following works, however:
gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 9AD8FC4162D7937CF64F972E1889D5F0E0636F49
I had keyserver hkps://keys.openpgp.org
configured in ~/.gnupg/dirmngr.conf
, which I'm pretty sure was the default in several previous version of GPG. It seems as if keyserver.ubuntu.com has become the new default keyserver though, so I guess just switching to that fixes the issue. It seems crazy how error prone and user-unfriendly AUR key management is though.
tarball commented on 2023-04-07 13:01 (UTC) (edited on 2023-04-07 13:01 (UTC) by tarball)
Run
$ gpg --recv-keys 9AD8FC4162D7937CF64F972E1889D5F0E0636F49
cbb commented on 2023-04-07 12:58 (UTC)
This package is failing to install for me since it was moved to AUR. If I run e.g. yay
to update, the following error occurs:
==> Verifying source file signatures with gpg...
units-2.22.tar.gz ... FAILED (unknown public key 1889D5F0E0636F49)
==> ERROR: One or more PGP signatures could not be verified!
-> error downloading sources: ~/.cache/yay/units
context: exit status 1
:: (1/1) Parsing SRCINFO: units
gpg: error reading key: No public key
:: PGP keys need importing:
-> 9AD8FC4162D7937CF64F972E1889D5F0E0636F49, required by: units
:: Import? [Y/n] y
:: Importing keys with gpg...
gpg: key E0636F49: no user ID
gpg: Total number processed: 1
-> problem importing keys
tarball commented on 2023-04-05 06:05 (UTC)
I really don't think (re)placing /usr/bin/pager
in a totally unrelated package is a good idea. Although nothing from official repositories provides it at this moment, it sounds like a recipe for conflicts.
We could probably add a wrapper script that finds the best pager (similar to Debian's /usr/bin/sensible-pager
), sets the $PAGER
environment variable if it's unset, and then calls the real binary (which would have to be renamed in this case).
Let me think about this for a few days.
fbrennan commented on 2023-04-05 00:36 (UTC)
Please symlink /usr/bin/pager to $PAGER by default, or, if unset, /usr/bin/less if it exists, else error. Help function doesn't work right without it.
Pinned Comments
tarball commented on 2024-12-02 21:49 (UTC)
Sorry for the silence, I've been out of town for a few days. The key @Ranguvar mentioned is indeed the one that worked when updating the package. GPG issues are getting tiresome, honestly.
Here's the command in case the comment is changed or removed: