[SOLVED] pacman -Sy gnupg archlinux-keyring manjaro-keyring fails

warning: gnupg-2.2.15-1 is up to date -- reinstalling
warning: archlinux-keyring-20190123-2 is up to date -- reinstalling
warning: manjaro-keyring-20180607-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (3)             Old Version  New Version  Net Change

core/archlinux-keyring  20190123-2   20190123-2     0.00 MiB
core/gnupg              2.2.15-1     2.2.15-1       0.00 MiB
core/manjaro-keyring    20180607-1   20180607-1     0.00 MiB

Total Installed Size:  11.12 MiB
Net Upgrade Size:       0.00 MiB

:: Proceed with installation? [Y/n] 
(3/3) checking keys in keyring                                               [############################################] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
downloading required keys...
error: key "EEEEE2EEEE2EEEEE" could not be looked up remotely
error: key "6D1655C14CE1C13E" could not be looked up remotely
error: key "CAA6A59611C7F07E" 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.

All this after reinstall spotify

    spotify-1.0.98.78-Release ... FAILED (unknown public key A87FF9DF48BF1C90)
==> ERROR: One or more PGP signatures could not be verified!
==> ERROR: Makepkg was unable to build spotify.

Three U.S. West coast servers tried
Referenced: https://wiki.manjaro.org/index.php?title=Pacman_troubleshooting

Did you note this warning msg? Or did you previously do this?
Please continue referencing and giving it a fair go at troubleshooting but it may be wise to begin double checking against the Arch wiki when messing with pacman in general; specifically, Arch based distros tend to breakapart at the seams the moment you begin to update using -Sy rather than -Syu for the (contracted) reasoning you are not guaranteed to update your entire system and the dependencies for your installed packages successfully. And to add on that, it is good practice to fully upgrade your system [ sudo pacman -Syu ] before making any additional changes or installations

Also: (SOLVED) ==> ERROR: One or more PGP signatures could not be verified!

https://wiki.manjaro.org/index.php/Pacman_troubleshooting#Errors_about_Keys

Yes 'pacman-key --init' was run.

All manjaro systems are updated daily, with 'yaourt -Syyuua', this was a re-install due to spotify fail. This problem has persisted through three daily updates. spotify re-install test on archlinux system did not fail.

Both methods plus trying different repos were tried from https://wiki.manjaro.org/index.php
/Pacman_troubleshooting#Errors_about_Keys

Thanks for the suggestions... .. .

FYI


:hugs:

Why are you using both upgrade and down grade commands to upgrade you only need to sudo pacman -Syyu to upggrade the only time to use the syyuu is to downgrade that is usually if you have updated from testing and broke manjaro.
I strongly recommend Syyu over Syu as it forces the mirrors to resync.

8 posts were split to a new topic: Is there a benefit to using pacman -Syyu over pacman -Syu

Also...

pacman -Sy PACKAGE is heavily the wrong way to install packages.

https://wiki.archlinux.org/index.php/System_maintenance#Partial_upgrades_are_unsupported

(Which is kinda OK for the specific key fix action .. but not for any other packages and needs more)

Edit. OK So I see this is partially coming from the Marginal Trust FAQ page..

Which could do with a slight modification, as we dont want to skip the update part of this. Maybe I will go over there for that though ..

2 Likes

So I dropped /etc/pacman.d/gnupg installed gnupg & archlinux-keyring which went no problems, how ever when I went to install manjaro-keyring this happened:

$ sudo pacman -Sy manjaro-keyring
:: Synchronizing package databases...
--2019-05-15 12:15:05--  http://distro.ibiblio.org/manjaro/stable/core/x86_64/core.db
Resolving distro.ibiblio.org (distro.ibiblio.org)... 152.19.134.43
Connecting to distro.ibiblio.org (distro.ibiblio.org)|152.19.134.43|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 153039 (149K) [application/octet-stream]
Saving to: \u2018/var/lib/pacman/sync/core.db.part\u2019

/var/lib/pacman/sync/core.d 100%[==========================================>] 149.45K   560KB/s    in 0.3s    

2019-05-15 12:15:05 (560 KB/s) - \u2018/var/lib/pacman/sync/core.db.part\u2019 saved [153039/153039]

--2019-05-15 12:15:05--  http://distro.ibiblio.org/manjaro/stable/core/x86_64/core.db.sig
Resolving distro.ibiblio.org (distro.ibiblio.org)... 152.19.134.43
Connecting to distro.ibiblio.org (distro.ibiblio.org)|152.19.134.43|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2019-05-15 12:15:05 ERROR 404: Not Found.

--2019-05-15 12:15:07--  http://distro.ibiblio.org/manjaro/stable/extra/x86_64/extra.db
Resolving distro.ibiblio.org (distro.ibiblio.org)... 152.19.134.43
Connecting to distro.ibiblio.org (distro.ibiblio.org)|152.19.134.43|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1881166 (1.8M) [application/octet-stream]
Saving to: \u2018/var/lib/pacman/sync/extra.db.part\u2019

/var/lib/pacman/sync/extra. 100%[==========================================>]   1.79M  2.71MB/s    in 0.7s    

2019-05-15 12:15:08 (2.71 MB/s) - \u2018/var/lib/pacman/sync/extra.db.part\u2019 saved [1881166/1881166]

--2019-05-15 12:15:08--  http://distro.ibiblio.org/manjaro/stable/extra/x86_64/extra.db.sig
Resolving distro.ibiblio.org (distro.ibiblio.org)... 152.19.134.43
Connecting to distro.ibiblio.org (distro.ibiblio.org)|152.19.134.43|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2019-05-15 12:15:08 ERROR 404: Not Found.

--2019-05-15 12:15:11--  http://distro.ibiblio.org/manjaro/stable/community/x86_64/community.db
Resolving distro.ibiblio.org (distro.ibiblio.org)... 152.19.134.43
Connecting to distro.ibiblio.org (distro.ibiblio.org)|152.19.134.43|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5481221 (5.2M) [application/octet-stream]
Saving to: \u2018/var/lib/pacman/sync/community.db.part\u2019

/var/lib/pacman/sync/commun 100%[==========================================>]   5.23M  4.40MB/s    in 1.2s    

2019-05-15 12:15:12 (4.40 MB/s) - \u2018/var/lib/pacman/sync/community.db.part\u2019 saved [5481221/5481221]

--2019-05-15 12:15:12--  http://distro.ibiblio.org/manjaro/stable/community/x86_64/community.db.sig
Resolving distro.ibiblio.org (distro.ibiblio.org)... 152.19.134.43
Connecting to distro.ibiblio.org (distro.ibiblio.org)|152.19.134.43|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2019-05-15 12:15:12 ERROR 404: Not Found.

--2019-05-15 12:15:14--  http://distro.ibiblio.org/manjaro/stable/multilib/x86_64/multilib.db
Resolving distro.ibiblio.org (distro.ibiblio.org)... 152.19.134.43
Connecting to distro.ibiblio.org (distro.ibiblio.org)|152.19.134.43|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 188519 (184K) [application/octet-stream]
Saving to: \u2018/var/lib/pacman/sync/multilib.db.part\u2019

/var/lib/pacman/sync/multil 100%[==========================================>] 184.10K   666KB/s    in 0.3s    

2019-05-15 12:15:15 (666 KB/s) - \u2018/var/lib/pacman/sync/multilib.db.part\u2019 saved [188519/188519]

--2019-05-15 12:15:15--  http://distro.ibiblio.org/manjaro/stable/multilib/x86_64/multilib.db.sig
Resolving distro.ibiblio.org (distro.ibiblio.org)... 152.19.134.43
Connecting to distro.ibiblio.org (distro.ibiblio.org)|152.19.134.43|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2019-05-15 12:15:15 ERROR 404: Not Found.

warning: manjaro-keyring-20180607-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (1)           Old Version  New Version  Net Change

core/manjaro-keyring  20180607-1   20180607-1     0.00 MiB

Total Installed Size:  0.14 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                     [#####################################] 100%
downloading required keys...
error: key "CAA6A59611C7F07E" 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.
[ljohnson@KISE-004 spotify]$

Please read the post I linked to. It has a series of steps.

[ljohnson@KISE-004 spotify]$ gpg --recv-key A87FF9DF48BF1C90
gpg: keyserver receive failed: Server indicated a failure
[ljohnson@KISE-004 spotify]$ sudo gpg --recv-key A87FF9DF48BF1C90
gpg: keyserver receive failed: Server indicated a failure

This is also covered in the second post of the thread Issues with "signature is marginal trust" or "invalid or corrupted package".

If you want a series of copy-and-paste steps please say so.

A post was merged into an existing topic: Is there a benefit to using pacman -Syyu over pacman -Syu

I suggest you change your mirror.
Do a manual check at repo.manajro.org and pick one that suits your needs.
Set it at the top of your mirrorlist and try again. (even after you solve your current issue...).
Or use Manjaro One Mirror Sync (m1ms).

Note: I hope I won't be flagged as an ad spammer!! :laughing:

1st Thanks Jonathon
2nd For the record, this system is updated every morning, along with two other Manjaro systems and two Archlinux systems.
3rd Mirrors are usually

::INFO Writing mirror list
::United_States   : https://mirrors.ocf.berkeley.edu/manjaro/stable/$repo/$arch
::United_States   : https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
::United_States   : http://distro.ibiblio.org/manjaro/stable/$repo/$arch


I am trying to re-install spotify to cure a problem with it - loss of audio - which happens from time to time and a re-install fixes the problem.

Set the mirror to https://mirror.philpot.de/manjaro/...
Removed archlinux-keyring-20181218-* (3) & manjaro-keyring-* (1) from /var/cache/pacman/pkg/
Reran the 'nuclear option'
Then got to this inexplicable error...

$ sudo pacman-key --refresh-keys
gpg: refreshing 129 keys from hkps://hkps.pool.sks-keyservers.net
gpg: keyserver refresh failed: Server indicated a failure
==> ERROR: A specified local key could not be updated from a keyserver.

Console out at https://pastebin.com/Wu80txcC

I thought it advisable it sort this error before moving on..?

BTW when I check the erreant Public Key on my workstation, an archlinux system I get this...

[--ljohnson{11:13:18}~]$ sudo gpg --recv-key A87FF9DF48BF1C90
gpg: key A87FF9DF48BF1C90: "Spotify Public Repository Signing Key <tux@spotify.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

Downloading gpa and looking at keys on 004 (the problem system) and 066 (recent new Manjaro install on remote server) shows just few on 004 not the large number on 066.

This tells me that the key system on 004 is in collapse and I am not sure how to restore it.

Some help would be appreciated.

Try this it works for me not sure where it comes from some dev posted it and it seems it works every time.

mkdir -p /home/username/.gnupg
echo 'keyring /etc/pacman.d/gnupg/pubring.gpg' >> $HOME/.gnupg/gpg.conf
chown -R username:username /home/username/.gnupg
chmod 700 /home/username/.gnupg
chmod 600 /home/username/.gnupg/*
1 Like

SOLVED

problem was mis-configured network, I dropped NetworkManager and went to netctl

apparently domain name lookup is not as expected in GnuPG
and
successful pinging the key-server is not an adequate test of connectivity
and "Server indicated a failure" is misleading.

All update process and receiving key operating properly

2 Likes