Arch Linux

schard

Forum Moderator

From: Hannover

Registered: 2016-05-06

Posts: 1,985

Website

[SOLVED] key "139B09DA5BF0D338" could not be looked up remotely

I currently cannot upgrade my system:

 pacman -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (1) libcap-2.65-1

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

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

The mirror is up-to-date.
I also tried several other mirrors.
Same issue with all of them.

Related (but different topic): https://bbs.archlinux.org/viewtopic.php?id=278389

I, once again, was too quick to post.
Solved with:

# pacman-key --init; pacman-key --populate archlinux

Last edited by schard (2022-07-26 12:14:01)

---

macro_rules! yolo { { $($tokens:tt)* } => { unsafe { $($tokens)* } }; }

Allan

Pacman

From: Brisbane, AU

Registered: 2007-06-09

Posts: 11,390

Website

Re: [SOLVED] key "139B09DA5BF0D338" could not be looked up remotely

pacman -S archlinux-keyring; pacman -Su

---

PGP Key: F99FFE0FEAE999BD

duanev

Member

Registered: 2012-02-26

Posts: 14

Re: [SOLVED] key "139B09DA5BF0D338" could not be looked up remotely

Same error, different key, but still Mr. Runge's: key "9B7A287D9A2EC608" could not be looked up remotely.

Tried all the above, pacman refuses to get past Mr. Runge's key regardless import attempt or not.

Another difference: I'm booted off of an install USB key (archlinux-2023.10.14-x86_64.iso) and I'm attempting to repair the local disk because pacman is out of sync with GLIBC versions.  Using pacman thusly (with proc, sys, dev, and boot partition mounted):

# pacman --sysroot /mnt -Syu

as described by https://wiki.archlinux.org/title/Pacman.
Btw, --sysroot is an invalid option for pacman-key.