Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update problem first install #91

Closed
G3NSVRV opened this issue Jun 28, 2019 · 11 comments
Closed

Update problem first install #91

G3NSVRV opened this issue Jun 28, 2019 · 11 comments

Comments

@G3NSVRV
Copy link

G3NSVRV commented Jun 28, 2019

IMPORTANT
Please read README and Known issues before creating the issue.

Please fill out the below information:
Describe the issue

100%(58/58) checking keys in keyring                                         [########################################] 100%warning: Public keyring not found; have you run 'pacman-key --init'?
downloading required keys...
error: key "BBE43771487328A9" could not be looked up remotely
error: key "94657AB20F2A092B" could not be looked up remotely
error: key "EEEEE2EEEE2EEEEE" could not be looked up remotely
error: key "4A1AFC345EBE18F8" could not be looked up remotely
error: key "6D1655C14CE1C13E" could not be looked up remotely
error: key "7F2D434B9741E8AC" could not be looked up remotely
error: key "A6234074498E9CEE" could not be looked up remotely
error: key "51E8B148A9999C34" could not be looked up remotely
error: key "FC1B547C8D8172C8" could not be looked up remotely
error: key "A5E9288C4FA415FA" could not be looked up remotely
error: key "771DF6627EDF681F" could not be looked up remotely
error: key "786C63F330D7CB92" could not be looked up remotely
error: key "1EB2638FF56C0C53" 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.

To Reproduce
Steps to reproduce the behavior:
pacman -Syu

Expected behavior
Upgrade everything without problems

Screenshots
If applicable, add screenshots to help explain your problem.

Enviroment:

  • Windows build number: 10.0.18362.175
  • ArchWSL version: ArchWSL-AppX_19.3.19.1_x64
  • ArchWSL Installer type zip/appx/other clean/update: appx
  • Launcher version: wsldl, version 19031901 https://git.io/wsldl

Additional context
pacman-key --init did not resolve the issue.

@G3NSVRV
Copy link
Author

G3NSVRV commented Jun 28, 2019

well, after a few tries, it works doing this:

sudo rm -R /etc/pacman.d/gnupg/
sudo rm -R /root/.gnupg/ 
sudo rm -R /var/cache/pacman/pkg/
sudo gpg --refresh-keys
sudo pacman-key --init
sudo pacman-key --populate archlinux
sudo pacman-key --refresh-keys
sudo pacman -Syyu

https://forum.manjaro.org/t/cannot-update-system-getting-invalid-or-corrupted-package-pgp-signature-error/24240/4

@yuk7
Copy link
Owner

yuk7 commented Jun 28, 2019

This is documented in the Wiki.

@Marietto2008
Copy link

it does not work for me :

[root@DESKTOP-N9UN2H3 c]# sudo pacman-key --refresh-keys
gpg: refreshing 116 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.

@CaydendW
Copy link

CaydendW commented Aug 28, 2020

@Marietto2008 I could not get this to work, but there is an Artix one that worked on my machine. Here is an Artix WSL. Maybe this isn't useful but I think Arch and Artix are close enough to have their differences overlooked. Just remember to run pacman-keys --init && pacman-keys --populate and it will work (hopefully).

@kickhad
Copy link

kickhad commented Dec 13, 2020

Thanks to @G3NSVRV
This fixed my Arch for WSL keyring issue.

https://gist.github.com/kickhad/f9e4a11c1835335a52eccacad02ad481

well, after a few tries, it works doing this:

sudo rm -R /etc/pacman.d/gnupg/
sudo rm -R /root/.gnupg/ 
sudo rm -R /var/cache/pacman/pkg/
sudo gpg --refresh-keys
sudo pacman-key --init
sudo pacman-key --populate archlinux
sudo pacman-key --refresh-keys
sudo pacman -Syyu

https://forum.manjaro.org/t/cannot-update-system-getting-invalid-or-corrupted-package-pgp-signature-error/24240/4

@DevPGSV
Copy link

DevPGSV commented Dec 25, 2020

sudo pacman-key --refresh-keys

The default keyserver sometimes doesn't work.
I had to use:
sudo pacman-key --keyserver ha.pool.sks-keyservers.net --refresh-keys

@nathanchere
Copy link

That's the same solution kickhad posted. It doesn't work for me. I still get

downloading required keys...
error: key "6D42BDD116E0068F" could not be looked up remotely
error: key "7258734B41C31549" could not be looked up remotely
error: key "3B94A80E50A477C7" 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.

@nathanchere
Copy link

This is documented in the Wiki.

This link is dead

@escape0707
Copy link

escape0707 commented Mar 31, 2021 via email

@Waxxx333
Copy link

Waxxx333 commented Sep 2, 2021

well, after a few tries, it works doing this:

sudo rm -R /etc/pacman.d/gnupg/
sudo rm -R /root/.gnupg/ 
sudo rm -R /var/cache/pacman/pkg/
sudo gpg --refresh-keys
sudo pacman-key --init
sudo pacman-key --populate archlinux
sudo pacman-key --refresh-keys
sudo pacman -Syyu

https://forum.manjaro.org/t/cannot-update-system-getting-invalid-or-corrupted-package-pgp-signature-error/24240/4

Worked perfectly. Thank you.

@mbledkowski
Copy link

This is documented in the Wiki.

it is not

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants