On Sun, Nov 06, 2011 at 10:36:17AM +, Peter Lewis wrote:
> But yes, this led me to to it. I had previously thought that all the
> keyservers
> synced with each other at some point, but apparently this isn't the case with
> keys.gnupg.net (at least). Sticking my key on that keyserver means that
Ah, thanks guys.
On Sat, 05 Nov 2011, Myra Nelson wrote:
> You need to import your key into the pacman-key database with sudo
> pacman-key --keysever pgp.mit.edu -r 22AD5874F39D989F, then everything
> shoud work fine.
I knew that this was an option, but wasn't sure why everyone else's key seemed
Am 06.11.2011 00:40, schrieb Peter Lewis:
> error: choqok: key "22AD5874F39D989F" is unknown
> error: failed to commit transaction (invalid or corrupted package (PGP
> signature))
> Errors occurred, no packages were upgraded.
I don't know, maybe it uses a broken keyserver.
Note that this is not
On Sat, Nov 5, 2011 at 18:40, Peter Lewis wrote:
> Hi,
>
> I've been trying to get to grips with the package signing stuff, and have
> just
> added my first signed package (choqok) to [community], but am having a
> problem
> installing it from the repo, when pacman doesn't already know about my
>
Hi,
I've been trying to get to grips with the package signing stuff, and have just
added my first signed package (choqok) to [community], but am having a problem
installing it from the repo, when pacman doesn't already know about my key. I'm
probably missing a step somewhere, or maybe I've found a
5 matches
Mail list logo
