Arch Linux User Repository

Probably a problem with your keyring. I just re-tested it with a freshly created unix user and it builds fine.

The build is failing due to a problem with the key in the comment below.

gpg: Note: signatures using the SHA1 algorithm are rejected
gpg: key 0x1889D5F0E0636F49: 2 bad signatures
gpg: key 0x1889D5F0E0636F49: no valid user IDs
gpg: this may be caused by a missing self-signature

People who wish to obtain the maintainer's key, can

gpg --fetch-keys 'https://savannah.gnu.org/people/viewgpg.php?user_id=33238'

after verifying user 33238 is the GNU maintainer for units.

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"

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.

Run

$ gpg --recv-keys 9AD8FC4162D7937CF64F972E1889D5F0E0636F49

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

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.

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.