You are not logged in.
Pages: 1
Some keys in archlinux32-keyring expired on short notice and were replaced / extended.
To get the latest keys, run
pacman-key --refresh-keysand update archlinux32-keyring before any other packages:
pacman -S archlinux32-keyring
pacman -SyuOffline
Thanks, that had been puzzling me for a little over a week as I recall. Thanks for the prompt workaround/fix - worked perfectly!
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
That first command above hangs forever on my system presumably because it is behind a firewall (which I have no control over) which is blocking the outbound hkp connection. How can I manually update those keys?
Offline
You can try the tipps on https://wiki.archlinux.org/index.php/Pa … mport_keys
I would try if switching the keyserver and using HTTP port 80 work.
Offline
That first command above hangs forever...
... not forever, only a minute or so, just be a little patient
Offline
... not forever, only a minute or so, just be a little patient
Yes I realized that later on after I posted. The command sits there for a ridiculously long time with no output so it seems to the user that it is hanging on a connection. So just crappy software design.
Offline
Right. At a guess on my old system it took more like 5 minutes to refresh keys. I considered posting to that effect, but the way you phrased your enquiry made it sound like you'd already diagnosed that your firewall was causing trouble.
At least the software does tell you what it's doing before it seems to hang. It would be nicer if it printed dots or something, but since this tool is just a wrapper for gpg's key management functions, I guess its to gpg's team you should make your complaint.
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
Pages: 1