On Tue, Dec 20, 2011 at 21:27, Peter Lewis wrote:
> On Wednesday 21 Dec 2011 01:36:35 Gaetan Bisson wrote:
> > [2011-12-20 19:38:19 +0530] Keshav P R:
> > > error: rekonq: key "22AD5874F39D989F" is unknown
> > > error: key "22AD5874F39D989F" could not be looked up remotely
>
> I opened a bug abou
On Wednesday 21 Dec 2011 03:15:58 Gaetan Bisson wrote:
> [2011-12-20 15:57:02 +] Peter Lewis:
> > I have my master key stored offline, and I hope it will last forever
>
> I see. It's just to bad that it is only 1024-bit long... RSA and DSA
> keys of this length will probably be crackable in te
[2011-12-20 15:57:02 +] Peter Lewis:
> Did this:
>
> % pacman-key -r 22AD5874F39D989F
>
> not work for you?
It seems like it does, but my ugly script had already imported your key.
--
Gaetan
[2011-12-20 15:57:02 +] Peter Lewis:
> I have my master key stored offline, and I hope it will last forever
I see. It's just to bad that it is only 1024-bit long... RSA and DSA
keys of this length will probably be crackable in ten/fifteen years.
(And I'm sure the NSA can already do it.)
--
G
On Wednesday 21 Dec 2011 01:36:35 Gaetan Bisson wrote:
> [2011-12-20 19:38:19 +0530] Keshav P R:
> > error: rekonq: key "22AD5874F39D989F" is unknown
> > error: key "22AD5874F39D989F" could not be looked up remotely
I opened a bug about this a couple of days ago: FS#27612.
> This seems to be Pete
[2011-12-20 20:36:02 +0530] Keshav P R:
> Now that I have refreshed the list of keys. How should I import them all?
You are confusing a bit of everything.
There are two ways to get the new keys into your pacman keyring:
- let pacman download them when you install packages signed by them;
- run my
On Tue, Dec 20, 2011 at 20:25, Gaetan Bisson wrote:
> [2011-12-20 20:19:13 +0530] Keshav P R:
> > There seems to be many new User IDs and Signatures. Should I do
> "pacman-key
> > --refresh-keys" periodically?
>
> Actually, `--refresh-keys` will only update signatures; to get the new
> keys you m
On Tue, Dec 20, 2011 at 20:20, Denis A. Altoé Falqueto <
denisfalqu...@gmail.com> wrote:
> On Tue, Dec 20, 2011 at 12:08 PM, Keshav P R
> wrote:
> > Hi all,
> > I am unable to upgrade community/rekonq from 0.8.0-1 to 0.8.1-1
> > due to
> >
> > error: rekonq: key "22AD5874F39D989F" is unkn
[2011-12-20 20:19:13 +0530] Keshav P R:
> There seems to be many new User IDs and Signatures. Should I do "pacman-key
> --refresh-keys" periodically?
Actually, `--refresh-keys` will only update signatures; to get the new
keys you must either import them from pacman as you install packages
signed b
On Tue, Dec 20, 2011 at 12:08 PM, Keshav P R
wrote:
> Hi all,
> I am unable to upgrade community/rekonq from 0.8.0-1 to 0.8.1-1
> due to
>
> error: rekonq: key "22AD5874F39D989F" is unknown
> error: key "22AD5874F39D989F" could not be looked up remotely
> error: failed to commit transactio
On Tue, Dec 20, 2011 at 20:06, Gaetan Bisson wrote:
> [2011-12-20 19:38:19 +0530] Keshav P R:
> > error: rekonq: key "22AD5874F39D989F" is unknown
> > error: key "22AD5874F39D989F" could not be looked up remotely
>
> This seems to be Peter Lewis signing with (one of his many) subkeys...
> (Not su
[2011-12-20 19:38:19 +0530] Keshav P R:
> error: rekonq: key "22AD5874F39D989F" is unknown
> error: key "22AD5874F39D989F" could not be looked up remotely
This seems to be Peter Lewis signing with (one of his many) subkeys...
(Not sure why he does that.)
Do `gpg --recv-key E19DAA50` (primary ID)
Hi all,
I am unable to upgrade community/rekonq from 0.8.0-1 to 0.8.1-1
due to
error: rekonq: key "22AD5874F39D989F" is unknown
error: key "22AD5874F39D989F" could not be looked up remotely
error: failed to commit transaction (invalid or corrupted package (PGP
signature))
Errors occurred,
13 matches
Mail list logo