You are not logged in.
This is a new system just installed yesterday. I have already tried different mirrors. Pacman reports all packages are up to date.
When I run
pacman -S pdnsdthis is what I get. Any idea why the keyring is "wrong"? Any workaround?
:: Retrieving packages...
pdnsd-1.2.9.a-13-x86_64 128.7 KiB 375K/s 00:00 [############################################################] 100%
(1/1) checking keys in keyring [############################################################] 100%
(1/1) checking package integrity [############################################################] 100%
error: pdnsd: signature from "Eli Schwartz <eschwartz@archlinux.org>" is unknown trust
:: File /var/cache/pacman/pkg/pdnsd-1.2.9.a-13-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] Last edited by danh337 (2018-12-24 01:20:59)
Offline
Not an Installation issue, moving to NC...
Offline
I just removed /etc/pacman.d/gnupg and did `pacman-key --init`, and now `pacman -S pdnsd` gives this.
:: Retrieving packages...
pdnsd-1.2.9.a-13-x86_64 128.7 KiB 882K/s 00:00 [############################################################] 100%
(1/1) checking keys in keyring [############################################################] 100%
downloading required keys...
:: Import PGP key 4096R/BD27B07A5EF45C2ADAF70E0484818A6819AF4A9B, "Eli Schwartz <eschwartz93@gmail.com>", created: 2016-05-03? [Y/n]
(1/1) checking package integrity [############################################################] 100%
error: pdnsd: signature from "Eli Schwartz <eschwartz@archlinux.org>" is unknown trust
:: File /var/cache/pacman/pkg/pdnsd-1.2.9.a-13-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.Offline
Your keyring *was* either broken or out of date, since my key was updated in the official keyring package about 2 months ago.
Now it is simply broken because you ran `pacman-key --init` to generate a new root key, but did not run `pacman-key --populate archlinux` to import the distribution keyring.
1) use --populate
2) post your /var/log/pacman.log
3) post the output of `pacman-key --list-sigs`
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
The `pacman-key --populate archlinux` fixed it. Thanks for helping @eschwartz.
This system is literally 1 day old, and I used the top 2 United States mirrors from the iso. My only guess is that those original mirrors were "too" old, maybe, and the keyring needed this full reset. I never had a problem like this before.
Offline
Which ISO? There is no "top two mirrors" since the mirrors are not ranked in any way. So if you were using the ISO from September or October, then your mirrorlist was old. And if your mirrorlist was old, then you could have potentially ended up using a broken mirror that has not synced in a long time. This is why the pacman-mirrorlist package provides you with a periodically updating list of currently active mirrors.
(Note that for the most part the age of the ISO does not matter as the only thing you use it for is the partitioning tools available on any Linux distribution, and the pacman binary which was last updated in July. It is actually possible to install Arch from another linux distro by using the "pacman", arch-install-scripts, and archlinux-keyring packages provided by Fedora, or the pacman package provided by Gentoo along with some additional work.)
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
The iso was ARCH_201810. The /etc/pacman.d/mirrorlist file in this iso has tons of mirrors from all different countries. There is some comment at the top, IIRC, about them being ranked somehow. But I just removed everything but the first 2 United States ones, which were:
Server = http://mirror.cs.pitt.edu/archlinux/$repo/os/$arch
Server = http://mirrors.sonic.net/archlinux/$repo/os/$archSo I guess this top mirror gives a messed up keyring. I didn't do anything outside of the steps outlined in the Arch Installation Guide wiki page.
I have installed Arch dozens of times and this is the first headache I've had related to keyring. If what you say is true that the age of the ISO doesn't matter, then I don't see how this problem could be avoided. It seems the age matters at least for the initial mirrorlist file.
Offline
I looked in the squashfs on the iso and here's the top of the mirrorlist:
##
## Arch Linux repository mirrorlist
## Filtered by mirror score from mirror status page
## Generated on 2018-10-01
##
## Hong Kong
Server = http://mirror.xtom.com.hk/archlinux/$repo/os/$arch
## Finland
Server = http://arch.mirror.far.fi/$repo/os/$arch
## Russia
Server = http://mirror.truenetwork.ru/archlinux/$repo/os/$arch
[. . .]Offline