Skip to main content
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED]Issue with updating due to keys, can't be solved with previous solutions (Read 832 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

[SOLVED]Issue with updating due to keys, can't be solved with previous solutions

Alright, I'll let the output speak for itself. It couldn't be solved with the solution in https://forum.artixlinux.org/index.php/topic,4376.0.html

Code: [Select]
[user@hale-bopp ~]$ sudo pacman -Syyu               
[sudo] password for user:
:: Synchronising package databases...
 system                261,2 KiB   628 KiB/s 00:00 [######################] 100%
 world                   2,0 MiB  18,0 MiB/s 00:00 [######################] 100%
 galaxy                  2,5 MiB  26,6 MiB/s 00:00 [######################] 100%
 extra                1709,4 KiB  4,10 MiB/s 00:00 [######################] 100%
 community               6,7 MiB  14,6 MiB/s 00:00 [######################] 100%
 universe              203,0 KiB   256 KiB/s 00:01 [######################] 100%
:: Starting full system upgrade...
warning: gnupg: local (2.3.1-1) is newer than system (2.2.36-1)
resolving dependencies...
looking for conflicting packages...

Packages (14) haskell-hslua-2.2.0-10  haskell-hslua-module-doclayout-1.0.4-33
              haskell-hslua-module-path-1.0.1-37
              haskell-hslua-module-system-1.0.1-36
              haskell-hslua-module-text-1.0.1-36
              haskell-hslua-module-version-1.0.1-37
              haskell-hslua-packaging-2.2.0.1-1
              haskell-pandoc-lua-marshal-0.1.6-7  liferea-1.13.9-1
              luajit-2.1.0.beta3.r439.g633f265f-1  mesa-22.1.6-1
              pandoc-2.18-18  tor-0.4.7.8-2  vulkan-radeon-22.1.6-1

Total Installed Size:  164,58 MiB
Net Upgrade Size:        0,07 MiB

:: Proceed with installation? [Y/n] y
(14/14) checking keys in keyring                   [######################] 100%
downloading required keys...
:: Import PGP key 786C63F330D7CB92, "Felix Yan <[email protected]>"? [Y/n] y
error: key "786C63F330D7CB92" could not be looked up remotely
:: Import PGP key 1247D995F165BBAC, "Artix Build Bot <[email protected]>"? [Y/n] y
error: key "1247D995F165BBAC" could not be looked up remotely
:: Import PGP key 06096A6AD1CEDDAC, "Laurent Carlier <[email protected]>"? [Y/n] y
error: key "06096A6AD1CEDDAC" 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.
[user@hale-bopp ~]$

I tried looking around for a prior solution, and I later discovered that a dependency of GnuPG isn't working properly due to a missing library.

Code: [Select]
[user@hale-bopp ~]$ sudo gpg --recv-key "06096A6AD1CEDDAC"
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
gpg: error running '/usr/bin/dirmngr': probably not installed
gpg: failed to start dirmngr '/usr/bin/dirmngr': Configuration error
gpg: can't connect to the dirmngr: Configuration error
gpg: keyserver receive failed: No dirmngr
[user@hale-bopp ~]$ dirmngr
dirmngr: error while loading shared libraries: libldap-2.4.so.2: cannot open shared object file: No such file or directory
[user@hale-bopp ~]$
Now, this problem prevents me from basically installing anything new. Anyone who knows how I could solve it?

 

Re: Issue with updating due to keys, can't be solved with previous solutions

Reply #1
Your gpg version appears to be wrong. It should be 2.2.36 not a development version.

Re: Issue with updating due to keys, can't be solved with previous solutions

Reply #2
Your gpg version appears to be wrong. It should be 2.2.36 not a development version.
Right. It's been getting that warning for quite a while but never bothered to look into it since it has worked fine until recently.
Oh well, temporarily disabling signature checking and then install GnuPG from the repo did the trick, at least after I had refreshed and repopulated the keys as well. Solved.