Arch Linux User Repository

is literally shorter.

Ah! My bad, I naively tried keyserver with https://keyserver.ubuntu.com . I was lazy in not working out what the protocol should be, not in typing. Bad form on my part.

The default keyservers that most people use in GPG are the SKS Keyserver Pool

This is useful to know. Thanks for the info!

For those struggling to import the key, it appears this key isn't in whatever default keyservers I have set up in GPG

For most users, it's not that the key isn't in the servers, but that the servers themselves no longer exist on the internet.

The default keyservers that most people use in GPG are the SKS Keyserver Pool, which was completely shut down earlier this month (after a few years of neglect). If you get a "No name" error, that's because GPG couldn't find the server in DNS anymore.

(Most of the individual servers that previously comprised the SKS pool are still alive – if Ubuntu's server is missing some keys, then pgp.rediris.es and pgp.surf.nl is probably a good second choice.)

And someone really ought to put all this GPG stuff in the AUR wiki article, instead of repeating it in every single AUR comment thread...

(It's probably better to add the ubuntu keyserver but I was lazy)

gpg --keyserver hkps://keyserver.ubuntu.com --recv-key ... is literally shorter. Though, it probably fetches the same URL anyway...

For those struggling to import the key, it appears this key isn't in whatever default keyservers I have set up in GPG. The key does appear in the ubuntu keyservers though. I imported with;

$ gpg --fetch-keys https://keyserver.ubuntu.com/pks/lookup\?op\=get\&search\=0xcd0a6e3cbb6768800b0736a8e7677380f54fd8a9

(It's probably better to add the ubuntu keyserver but I was lazy)

fwiw, the key belongs to raven@themaw.net who does appear to be contributor to autofs, although that doesn't prove much by itself.

I'll also echo the disappointment about autofs being moved to AUR. I'll have to look into systemd automount, but from what I can tell it's going to be a pain. Not to mention that I use SSSD provisioned autofs.

like others, why was it moved to AUR? also I confirm the PGP error on x86_64 arch.

@BlindTreeFrog - Can confirm I get the same "ERROR: One or more PGP signatures could not be verified!" error. That said I am running it on ARMV6 Raspberry Pi board.

(And have been successfully running for a few years now, till only today I built a new image and was confused why Pacman did not resolve it. Scratching my head for a while I see it in the AUR)

I second why on earth this was moved to AUR. I had assumed it would be used by loads of people.

There is absolutely no excuse whatsoever for this to be moved to the AUR. From what I can see, it still has active development (I see current patches) and even though systemd automount exists, Arch should not be enforcing a single way of doing things.

In addition, by moving this to the AUR, that gives people that already had it installed a false impression that it's up to date, and in actuality anyone who had this installed beforehand that didn't check to see if it's in the AUR, have an unpatched package installed and could potentially be open to CVE's they weren't open to before.

I'm getting key errors when attempting to verify this. Is there a key server I'm missing?

I guess for Spring cleanup '21 https://lists.archlinux.org/pipermail/arch-dev-public/2021-May/030419.html as I don't see autofs in Barthalion's orphan packages or Alad dropped packages

Why has this been dropped to AUR?

Why was this dropped from the official repos? This is a lot better than the systemd automount :/