Entry tags:
[geek] debian's gpg verification has been pissing me off
This situation would be far better if the error included a url that told you what to do about it.
One of the errors:
W: GPG error: http://http.us.debian.org testing Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 010908312D230C5F
The solution:
gpg --keyserver pgp.mit.edu --recv-keys 010908312D230C5F
gpg -a --export 010908312D230C5F | apt-key add -
And it's not even like I'm not familiar with public key cryptography, or gpg in particular. I've coordinated a bunch of keysigning parties and written multiple programs to make pretty pictures out of the results.
One of the errors:
W: GPG error: http://http.us.debian.org testing Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 010908312D230C5F
The solution:
gpg --keyserver pgp.mit.edu --recv-keys 010908312D230C5F
gpg -a --export 010908312D230C5F | apt-key add -
And it's not even like I'm not familiar with public key cryptography, or gpg in particular. I've coordinated a bunch of keysigning parties and written multiple programs to make pretty pictures out of the results.
