You are not logged in.

#1 2022-08-10 14:31:19

mahdi_zojaji
Member
Registered: 2022-08-10
Posts: 12

PGP key could not be looked up remotely[solved]

Hi
when i call this command:

 sudo pacman -Syu 

i got this result:

➜  ~ sudo pacman -Syu                 
[sudo] password for mahdi: 
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 archlinuxcn is up to date
 archlinuxir is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (15) containerd-1.6.8-1  firefox-103.0.2-1  gdk-pixbuf2-2.42.9-1  graphviz-5.0.0-2  intel-ucode-20220809-1
              lib32-systemd-251.4-1  libevent-2.1.12-2  paru-1.11.1-1  rsync-3.2.5pre2-1  systemd-251.4-1
              systemd-libs-251.4-1  systemd-sysvcompat-251.4-1  tracker3-3.3.3-1  wpebackend-fdo-1.12.1-1
              xdg-user-dirs-0.18-1

Total Download Size:     2.32 MiB
Total Installed Size:  409.61 MiB
Net Upgrade Size:        0.90 MiB

:: Proceed with installation? [Y/n] Y
:: Retrieving packages...
 paru-1.11.1-1-x86_64                                                                  2.3 MiB   229 KiB/s 00:10 [####################################################################] 100%
(15/15) checking keys in keyring                                                                                 [####################################################################] 100%
downloading required keys...
:: Import PGP key 9C02FF419FECBE16, "Morten Linderud <foxboron@archlinux.org>"? [Y/n] Y
error: key "9C02FF419FECBE16" could not be looked up remotely
:: Import PGP key 3B94A80E50A477C7, "Jan Alexander Steffens (heftig) <heftig@archlinux.org>"? [Y/n]Y
error: key "3B94A80E50A477C7" could not be looked up remotely
:: Import PGP key 6D42BDD116E0068F, "Christian Hesse <eworm@archlinux.org>"? [Y/n]Y
error: key "6D42BDD116E0068F" could not be looked up remotely
:: Import PGP key 539DFD48135182EF, "Juergen Hoetzel <juergen@archlinux.org>"? [Y/n] Y
error: key "539DFD48135182EF" could not be looked up remotely
:: Import PGP key F9F9FA97A403F63E, "lilac (on behalf of Jiachen Yang) <farseerfc@gmail.com>"? [Y/n] Y
error: key "F9F9FA97A403F63E" 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.

and when i want install archlinux-keyring i got this result:

➜  ~ sudo pacman -Sy archlinux-keyring             
[sudo] password for mahdi: 
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 archlinuxcn                                                                        1937.3 KiB  85.5 KiB/s 00:23 [####################################################################] 100%
 archlinuxir                                                                          95.7 KiB  39.3 KiB/s 00:02 [####################################################################] 100%
resolving dependencies...
looking for conflicting packages...

Packages (1) archlinux-keyring-20220727-1

Total Installed Size:  1.55 MiB

:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring                                                                                   [####################################################################] 100%
downloading required keys...
:: Import PGP key 6D42BDD116E0068F, "Christian Hesse <eworm@archlinux.org>"? [Y/n] Y
error: key "6D42BDD116E0068F" 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.

Last edited by mahdi_zojaji (2022-11-05 16:02:05)

Offline

#2 2022-08-10 14:36:16

Scimmia
Fellow
Registered: 2012-09-01
Posts: 9,830

Re: PGP key could not be looked up remotely[solved]

How long since the last time you updated?

Offline

#3 2022-08-10 14:47:12

mahdi_zojaji
Member
Registered: 2022-08-10
Posts: 12

Re: PGP key could not be looked up remotely[solved]

Scimmia wrote:

How long since the last time you updated?

Less than a week

Offline

#4 2022-08-10 14:54:46

Scimmia
Fellow
Registered: 2012-09-01
Posts: 9,830

Re: PGP key could not be looked up remotely[solved]

Then how come pacman doesn't give a warning that archlinux-keyring is already up to date?

Something is really strange here. It's almost like you wiped your pacman keyring, what does `pacman-key --list-keys` show? Even that would give the pacman warning I mentioned, though, so I really don't know.

Offline

#5 2022-08-10 15:06:40

mahdi_zojaji
Member
Registered: 2022-08-10
Posts: 12

Re: PGP key could not be looked up remotely[solved]

Scimmia wrote:

Then how come pacman doesn't give a warning that archlinux-keyring is already up to date?

Something is really strange here. It's almost like you wiped your pacman keyring, what does `pacman-key --list-keys` show? Even that would give the pacman warning I mentioned, though, so I really don't know.

I went all the way to solve this problem and ended up doing something dangerous.
I deleted this directory:
/etc/pacman.d/gnupg
And I also deleted Pacman's cache.

Last edited by mahdi_zojaji (2022-08-10 15:07:27)

Offline

#6 2022-08-10 15:07:55

Scimmia
Fellow
Registered: 2012-09-01
Posts: 9,830

Re: PGP key could not be looked up remotely[solved]

Offline

#7 2022-08-10 15:10:21

seth
Member
Registered: 2012-09-03
Posts: 33,675

Re: PGP key could not be looked up remotely[solved]

Also

pacman -Qikk archlinux-keyring archlinuxcn-keyring


Edit: fuck.

Last edited by seth (2022-08-10 15:10:50)

Online

#8 2022-08-10 15:11:55

mahdi_zojaji
Member
Registered: 2022-08-10
Posts: 12

Re: PGP key could not be looked up remotely[solved]

Scimmia wrote:

i did that.

but when i call

sudo pacman-key --populate

i got this error:

==> ERROR: No keyring files exist in /usr/share/pacman/keyrings.

Offline

#9 2022-08-10 15:17:34

Scimmia
Fellow
Registered: 2012-09-01
Posts: 9,830

Re: PGP key could not be looked up remotely[solved]

So that combined with the lack of a warning from pacman means you don't even have archlinux-keyring installed. What in the world did you do to this system?

I would say to reinstall it from your cache where it should have already been verified, but who knows what you've got left there at this point. Give it a shot with pacman -U /var/cache/pacman/pkg/<package>

Offline

#10 2022-08-10 15:18:07

seth
Member
Registered: 2012-09-03
Posts: 33,675

Re: PGP key could not be looked up remotely[solved]

Did you run "sudo pacman-key --init" first?

Online

#11 2022-08-10 15:20:41

mahdi_zojaji
Member
Registered: 2022-08-10
Posts: 12

Re: PGP key could not be looked up remotely[solved]

seth wrote:

Did you run "sudo pacman-key --init" first?

Yes i did

Offline

#12 2022-08-10 15:29:07

seth
Member
Registered: 2012-09-03
Posts: 33,675

Re: PGP key could not be looked up remotely[solved]

Well, return to

pacman -Qikk archlinux-keyring archlinuxcn-keyring

for "wtf has happened to your system"

Online

#13 2022-08-10 15:33:09

mahdi_zojaji
Member
Registered: 2022-08-10
Posts: 12

Re: PGP key could not be looked up remotely[solved]

seth wrote:

Well, return to

pacman -Qikk archlinux-keyring archlinuxcn-keyring

for "wtf has happened to your system"

output:

Name            : archlinux-keyring
Version         : 20220727-1
Description     : Arch Linux PGP keyring
Architecture    : any
URL             : https://gitlab.archlinux.org/archlinux/archlinux-keyring/
Licenses        : GPL3
Groups          : base-devel
Provides        : None
Depends On      : pacman
Optional Deps   : None
Required By     : base
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 1584.97 KiB
Packager        : Christian Hesse <eworm@archlinux.org>
Build Date      : Wed 27 Jul 2022 02:35:15 PM +0430
Install Date    : Wed 10 Aug 2022 07:57:19 PM +0430
Install Reason  : Explicitly installed
Install Script  : Yes
Validated By    : SHA-256 Sum

archlinux-keyring: 8 total files, 0 altered files
error: package 'archlinuxcn-keyring' was not found


and i have an bad idea but maybe help me.
change SigLevel = Never to install archlinux-keyring then back to the previous state.
are you agree with me?

Last edited by mahdi_zojaji (2022-08-10 15:33:40)

Offline

#14 2022-08-10 15:45:37

mahdi_zojaji
Member
Registered: 2022-08-10
Posts: 12

Re: PGP key could not be looked up remotely[solved]

it fixed.
i did:
1. change SigLevel in /etc/pacman.conf from

 SigLevel    = Required DatabaseOptional 

to

 SigLevel = Never

2. install keyring by

sudo pacman -Sy archlinux-keyring && sudo pacman -Su

3. reset keys

sudo pacman-key --init --keyserver hkps://keys.openpgp.org
sudo pacman-key --populate
sudo pacman-key --refresh-keys

4. update

pacman -Syu
pacman -Syyu

Offline

#15 2022-08-10 15:53:36

seth
Member
Registered: 2012-09-03
Posts: 33,675

Re: PGP key could not be looked up remotely[solved]

You had archlinux-keyring 20220727-1 installed and it's not corrupted, yet also "==> ERROR: No keyring files exist in /usr/share/pacman/keyrings." and "sudo pacman -Sy archlinux-keyring" wanted to update the package w/o telling you that it's up-to date already.
It also was installed 20 minutes ago, but your OP described an error.
None of this adds up - at all.

pacman -Syu
pacman -Syyu

is nonsense, don't run "pacman -Syyu" unless you know why you want to. It's an awesome way to corrupt your package database what might somehow have happened here. We'll probably never learn (except if there's anything in your pacman log)

Online

#16 2022-08-10 16:03:18

mahdi_zojaji
Member
Registered: 2022-08-10
Posts: 12

Re: PGP key could not be looked up remotely[solved]

seth wrote:

You had archlinux-keyring 20220727-1 installed and it's not corrupted, yet also "==> ERROR: No keyring files exist in /usr/share/pacman/keyrings." and "sudo pacman -Sy archlinux-keyring" wanted to update the package w/o telling you that it's up-to date already.
It also was installed 20 minutes ago, but your OP described an error.
None of this adds up - at all.

pacman -Syu
pacman -Syyu

is nonsense, don't run "pacman -Syyu" unless you know why you want to. It's an awesome way to corrupt your package database what might somehow have happened here. We'll probably never learn (except if there's anything in your pacman log)

oh yeah.
actually when i comment these:

#[archlinuxcn]
#SigLevel = Optional
#Server = http://repo.archlinuxcn.org/$arch

#[archlinuxir]
#SigLevel = Optional
#Server = https://mirror.bardia.tech/$repo/$arch

i don't have error on

sudo pacman -Syu

but when uncomment these i got error.

what can I do now? sad

Offline

#17 2022-08-10 16:08:13

seth
Member
Registered: 2012-09-03
Posts: 33,675

Re: PGP key could not be looked up remotely[solved]

Is archlinuxcn the only problematic one?
Install archlinuxcn-keyring and also post your pacman log.
Again: so far nothing in this thread really adds up, maybe the log can set the record straight.

Edit: https://wiki.archlinux.org/title/Unoffi … rchlinuxcn actually points out that requirement…

Last edited by seth (2022-08-10 16:09:51)

Online

#18 2022-08-10 16:10:44

mahdi_zojaji
Member
Registered: 2022-08-10
Posts: 12

Re: PGP key could not be looked up remotely[solved]

now:

➜  ~ sudo pacman-key --refresh-keys
gpg: error retrieving 'arch@eworm.de' via WKD: Server indicated a failure
gpg: error reading key: Server indicated a failure
gpg: error retrieving 'eworm@archlinux.org' via WKD: Server indicated a failure
gpg: error reading key: Server indicated a failure
gpg: refreshing 1 key from hkp://keyserver.ubuntu.com
gpg: keyserver refresh failed: Server indicated a failure
==> ERROR: Could not update key: A6234074498E9CEE
gpg: error retrieving 'george@rawlinson.net.nz' via WKD: Server indicated a failure
gpg: error reading key: Server indicated a failure
gpg: error retrieving 'grawlinson@archlinux.org' via WKD: Server indicated a failure
gpg: error reading key: Server indicated a failure
gpg: refreshing 1 key from hkp://keyserver.ubuntu.com
gpg: keyserver refresh failed: Server indicated a failure
==> ERROR: Could not update key: 25EA6900D9EA5EBC

Offline

#19 2022-08-10 16:20:09

seth
Member
Registered: 2012-09-03
Posts: 33,675

Re: PGP key could not be looked up remotely[solved]

Did you

seth wrote:

Install archlinuxcn-keyring and also post your pacman log.

Online

#20 2022-08-10 16:32:15

mahdi_zojaji
Member
Registered: 2022-08-10
Posts: 12

Re: PGP key could not be looked up remotely[solved]

seth wrote:

Did you

seth wrote:

Install archlinuxcn-keyring and also post your pacman log.

installed:

➜  ~ sudo pacman -S archlinuxcn-keyring

resolving dependencies...
looking for conflicting packages...

Packages (1) archlinuxcn-keyring-20220716-1

Total Download Size:   0.30 MiB
Total Installed Size:  0.41 MiB

:: Proceed with installation? [Y/n] Y
:: Retrieving packages...
 archlinuxcn-keyring-20220716-1-any           302.6 KiB  49.6 KiB/s 00:06 [##########################################] 100%
(1/1) checking keys in keyring                                            [##########################################] 100%
(1/1) checking package integrity                                          [##########################################] 100%
(1/1) loading package files                                               [##########################################] 100%
(1/1) checking for file conflicts                                         [##########################################] 100%
(1/1) checking available disk space                                       [##########################################] 100%
:: Processing package changes...
(1/1) installing archlinuxcn-keyring                                      [##########################################] 100%
==> Appending keys from archlinuxcn.gpg...
gpg: public key CF66D153D884358F is 16 seconds newer than the signature
==> Locally signing trusted keys in keyring...
  -> Locally signed 55 keys.
==> Importing owner trust values...
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
==> Disabling revoked keys in keyring...
  -> Disabled 8 keys.
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: public key CF66D153D884358F is 16 seconds newer than the signature
gpg: depth: 0  valid:   1  signed:  54  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:  54  signed:  90  trust: 0-, 0q, 0n, 54m, 0f, 0u
gpg: depth: 2  valid:  71  signed:  30  trust: 71-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2022-10-14
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: public key CF66D153D884358F is 16 seconds newer than the signature
gpg: depth: 0  valid:   1  signed:  54  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:  54  signed:  90  trust: 0-, 0q, 0n, 54m, 0f, 0u
gpg: depth: 2  valid:  71  signed:  30  trust: 71-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2022-10-14
Optional dependencies for archlinuxcn-keyring
    pkgstats: install to submit package usage statistics
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...

Offline

#21 2022-08-10 19:49:54

seth
Member
Registered: 2012-09-03
Posts: 33,675

Re: PGP key could not be looked up remotely[solved]

So does the issue remain after installing archlinuxcn-keyring or not?

Online

#22 2022-11-05 15:59:50

mahdi_zojaji
Member
Registered: 2022-08-10
Posts: 12

Re: PGP key could not be looked up remotely[solved]

Sorry I didn't continue this conversation.
I was busy solving the problem and unfortunately I forgot.
Now my problem is solved.

Offline

#23 2022-11-05 16:00:44

mahdi_zojaji
Member
Registered: 2022-08-10
Posts: 12

Re: PGP key could not be looked up remotely[solved]

Sorry I didn't continue this conversation.
I was busy solving the problem and unfortunately I forgot.
Now my problem is solved.

Offline

Board footer

Powered by FluxBB