On 09/10/2020 15.38, Doug Newgard via arch-general wrote: > > To get past the key error, use a working keyserver. hkps://keyserver.ubunut.com > seems to be pretty reliable. After changing keyserver I got similar error: [root@nettest ~]# pacman-key --refresh-keys --keyserver hkps://keyserver.ubuntu.com [...] gpg: depth: 0 valid: 1 signed: 6 trust: 0-, 0q, 0n, 0m, 0f, 1u gpg: depth: 1 valid: 6 signed: 80 trust: 0-, 0q, 0n, 6m, 0f, 0u gpg: depth: 2 valid: 68 signed: 20 trust: 68-, 0q, 0n, 0m, 0f, 0u gpg: next trustdb check due at 2020-10-11 ==> ERROR: A specified local key could not be updated from a keyserver. BUT then pacman -S archlinux-keyring succeeded! > If the system is more than a year old, pacman is too old to successfully update > the system anyway. I would suggest booting a recent install disk and using > pacman's --sysroot option or use pacman-static. I upgraded this system with old pacman and had well known error: error: hook /usr/share/libalpm/hooks/texinfo-remove.hook line 2: invalid value Path and reinstall all packages # pacman -Qqn | pacman -S - did the trick. Next I had to netctl reenable all profiles and it seems that everything is working now. Many thanks for help! Łukasz
