error: key - could not be imported

atomicpookavirus · 2015-06-01 17:32:54

I'm trying to update my arch install from 2013 and am getting some errors after running;

pacman -Syu...

:: Import PGP key 4096R/, "Anatol Pomozov <anatol.pomozov@gmail.com>", created: 2014-02-03? [Y/n] y
error: key "Anatol Pomozov <anatol.pomozov@gmail.com>" could not be imported
:: Import PGP key 4096R/, "Antonio Rojas <arojas@us.es>", created: 2014-10-21? [Y/n] y
error: key "Antonio Rojas <arojas@us.es>" could not be imported
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

( code tags added )

Last edited by atomicpookavirus (2015-06-01 18:11:06)

thiagowfx · 2015-06-01 17:50:11

Hey there, please use code tags to post output.

2013, huh? I believe you're facing one of those issues:

1. gpg migration to v2, in this case you should recreate your pacman gpg key database (see the manpage of pacman-key)
2. those keys are missing, so you can add them manually (pacman-key -r then pacman-key --lsign-key)

In either case, I remember those are documented elsewhere (older forum posts and Wiki). Try 1 first to see if it helps in any way.

karol · 2015-06-01 18:10:19

Is there any reason why not install anew?
There are other issues from mid-2013 that can cause a problem: https://www.archlinux.org/news/binaries … ervention/

atomicpookavirus · 2015-06-01 18:14:03

No reason, except to possibly save some time in configuring. Though, if enough things break, that doesn't matter.
I'm already prepping a USB drive with the latest arch to install on my desktop.

atomicpookavirus · 2015-06-01 18:23:42

thiagowfx wrote:

1. gpg migration to v2, in this case you should recreate your pacman gpg key database (see the manpage of pacman-key)

I don't see a reference to recreate database. The man page is rather sparse. Perhaps either --import or --updatedb?

Is the evo/lution installer a good way to save time installing arch? I may give that a try too.

jasonwryan · 2015-06-01 18:32:41

atomicpookavirus wrote:

Is the evo/lution installer a good way to save time installing arch? I may give that a try too.

No. It is not Arch so not supported here.

thiagowfx · 2015-06-01 18:33:51

atomicpookavirus wrote:

I don't see a reference to recreate database. The man page is rather sparse. Perhaps either --import or --updatedb?
Is the evo/lution installer a good way to save time installing arch? I may give that a try too.

1. Remove your GPG directory (probably /etc/pacman.d/gnupg, you can find out precisely which one in /etc/pacman.conf (the GPGDir setting) -- backup it first in case something goes wrong
2. pacman-key --init
3. pacman-key --populate archlinux

You'll then probably see errors such as

error: infinality-bundle: key "AE6866C7962DDE58" is unknown

after doing that -- in the case you use custom repos. Good news, at least. You can solve it by manually adding those keys (with what I said in my second point in my first post).

Last edited by thiagowfx (2015-06-01 18:34:16)

Archimaredes · 2015-07-19 20:35:20

Hiya, just had this same issue, fixed it by first doing:

# pacman -Sy archlinux-keyring

Then updating everything else:

# pacman -Su

The key wasn't importing because the keyring package was out of date.

kejingzhang · 2015-08-10 15:49:16

Archimaredes wrote:

Hiya, just had this same issue, fixed it by first doing:
# pacman -Sy archlinux-keyring
Then updating everything else:
# pacman -Su
The key wasn't importing because the keyring package was out of date.

It worked!

mrunion · 2015-08-10 20:38:19

You guys may want to find out why you have out of date packages. Do you "pacman -Syu" regularly?

severach · 2015-08-11 03:27:47

The easy way is to boot the new ArchISO and perform the upgrade with "pacman --root". Don't use arch-chroot which will be the same old version you have now.

Last edited by severach (2015-08-11 03:29:33)

Texas · 2015-08-12 13:13:46

karol wrote:

Is there any reason why not install anew?
There are other issues from mid-2013 that can cause a problem: https://www.archlinux.org/news/binaries … ervention/

I had this issue, got it fixed. Then more issues popped. I have not used this machine for 14 months. I guess I will re-install. I love Arch... but it is a "use it or lose it" distro.

janpansa · 2016-07-24 21:11:21

Archimaredes wrote:

Hiya, just had this same issue, fixed it by first doing:
# pacman -Sy archlinux-keyring
Then updating everything else:
# pacman -Su
The key wasn't importing because the keyring package was out of date.

You sir are a gentleman and a scholar !

Skyalmian · 2017-06-07 21:51:43

/updating archived / unused HDD since September 2014. After an hour of chewing through dependency conflicts and outdated keyring settings / stuff via searches, pacman -Su --force ('force' apparently needed) is updating 984.

Thank you for all the help / this thread. (y)

jasonwryan · 2017-06-07 22:01:54

Don't do that; using --force indiscriminately is a bad idea. So is necrobumping: https://wiki.archlinux.org/index.php/Co … bumping.22

Closing

Arch Linux

#1 2015-06-01 17:32:54

error: key - could not be imported

#2 2015-06-01 17:50:11

Re: error: key - could not be imported

#3 2015-06-01 18:10:19

Re: error: key - could not be imported

#4 2015-06-01 18:14:03

Re: error: key - could not be imported

#5 2015-06-01 18:23:42

Re: error: key - could not be imported

#6 2015-06-01 18:32:41

Re: error: key - could not be imported

#7 2015-06-01 18:33:51

Re: error: key - could not be imported

#8 2015-07-19 20:35:20

Re: error: key - could not be imported

#9 2015-08-10 15:49:16

Re: error: key - could not be imported

#10 2015-08-10 20:38:19

Re: error: key - could not be imported

#11 2015-08-11 03:27:47

Re: error: key - could not be imported

#12 2015-08-12 13:13:46

Re: error: key - could not be imported

#13 2016-07-24 21:11:21

Re: error: key - could not be imported

#14 2017-06-07 21:51:43

Re: error: key - could not be imported

#15 2017-06-07 22:01:54

Re: error: key - could not be imported

Board footer