You are not logged in.

#1 2014-12-18 07:58:07

SimFox3
Member
From: San Jose, Ca
Registered: 2014-01-04
Posts: 42
Website

linux-ck-ivybridge: key "88A032865EE46C4C" could not be looked up

Hi Guys,
Time for my weekly pacman update, and now I'm seeing this issue:

:: Retrieving packages ...
 autojump-22.2.2-1-any               27.6 KiB   790K/s 00:00 [################################] 100%
 nodejs-0.10.34-1-x86_64              3.9 MiB  7.50M/s 00:01 [################################] 100%
 linux-ck-ivybridge-3.18.1-1-x...    54.3 MiB  10.9M/s 00:05 [################################] 100%
 linux-ck-ivybridge-headers-3....     6.1 MiB  11.1M/s 00:01 [################################] 100%
 virtualbox-ck-host-modules-iv...   166.9 KiB  11.6M/s 00:00 [################################] 100%
(46/46) checking keys in keyring                             [################################] 100%
downloading required keys...
error: key "88A032865EE46C4C" could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

[root@Vaio-Saad ~]# pacman-key --lsign-key 5EE46C4C
  -> Locally signing key 5EE46C4C...
==> ERROR: 5EE46C4C could not be locally signed.

Trying to sign/download the 5EE46C4C key fails too. Any ideas?

Thanks

Offline

#2 2014-12-18 08:27:07

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: linux-ck-ivybridge: key "88A032865EE46C4C" could not be looked up

Offline

#3 2014-12-19 07:47:05

SimFox3
Member
From: San Jose, Ca
Registered: 2014-01-04
Posts: 42
Website

Re: linux-ck-ivybridge: key "88A032865EE46C4C" could not be looked up

Thanks, it was a combination of both my hotel room not allowing the port through, and a corrupted gnupg database. After I rebuilt the gnupg keys (--init / --populate) it started working.

Offline

#4 2014-12-19 08:04:10

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,404
Website

Re: linux-ck-ivybridge: key "88A032865EE46C4C" could not be looked up

You'll still need to re-add my key after rebuilding the db:

# pacman-key -r 5EE46C4C && pacman-key --lsign-key 5EE46C4C

CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#5 2014-12-19 10:10:17

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: linux-ck-ivybridge: key "88A032865EE46C4C" could not be looked up

Please remember to mark the thread as solved https://bbs.archlinux.org/viewtopic.php?id=130309

Offline

Board footer

Powered by FluxBB