Can confirm, it hasn't worked for two days for me. Are there any quick/temporary workarounds?

there is a known recurring bug in the keyring builder;
which recurred yesterday

there will be temporary interruption in the normal pacman
service today

The issue is resolved for me now, thanks :)

antalepo -

for the benefit of curious others, could you explain the how
issue is resolved for you now?

Right, sorry. I tried installing the affected packages again in the same way, and the signature checks passed. I assumed you fixed something on the server side. Nevertheless, the issue is back again today.

While the issue was present I was still able to install the affected packages by changing the following settings in the live ISO's /etc/pacman.conf:
[options]
SigLevel = Never
LocalFileSigLevel = Never

... which disables the signature checks. This is obviously a huge security risk, and it might've been foolish of me, but whatever. I didn't think the mirrors would serve malicious packages, and I was right (like I said above, they later passed the checks). I do not have these settings on my installed system.

To be clear, the issue was temporarily resolved from around the time of my last post to at least a while later. This was not related to me changing my config.

Facing this issue in installing packages for ARMv7.

bill-auger wrote:

there is a known recurring bug in the keyring builder;
which recurred yesterday

there will be temporary interruption in the normal pacman
service today

This doesn't seem to have solved it. Do we know what the bug is, and if so, how do we fix it? Can I help?

I've noticed the same problems on 2 machines since 10 days ago. The problem still remains. One thing not mentioned yet is that 'pacman --refresh-keys' doesn't work:

sudo pacman-key --refresh-keys 
gpg: refreshing 152 keys from hkps://hkps.pool.sks-keyservers.net
gpg: keyserver refresh failed: General error
==> ERROR: A specified local key could not be updated from a keyserver.

Not sure if the problems are related. Specifying a key server with '--keyserver hkp://pool.sks-keyservers.net' seems to refresh some keys, but after that the 'Signature from bill-auger is unknown trust' problem remains.

Is there a workaround that doesn't involve disabling the package signature checks?

ignoring the signatures is not the best work-around though; and it can not be recommended

davisr found a clever work-around, which verifies all signatures properly, though - that is to set the system clock to a date before the expiry (2020-11-06) before installing the troublesome packages

one could o/c download each package and verify the signatures manually, without making any changes to the host system

its an old known problem with the keyring package

yes, it could have had i dedicated bug report many months ago - there have been multiple BRs like this one; because of the same root cause - i just opened a new ticket for it #2931

Hey. I assume the installation mediums need to be updated with this fix?

I'm running into this with the Parabola SystemD CLI ISO x86_64.

yes, the ISO should be re-made; but the existing ones are still
usable - just upgrade the keyrings before running pacstrap

# pacman -Sy archlinux-keyring archlinux32-keyring parabola-keyring

https://wiki.parabola.nu/Installation_Guide

Hey. I tried that and also what the installation guide said, but ran into a similar issue as Mampir above when trying to refresh the keys. Only difference is that I get a "Server indicated a failure" instead of "General error".

I get the same with that other keyserver as well, but no change. I'm connected to the Internet. Not sure what's causing.

oh yes, i forgot about that - the netinstall ISOs are more broken than i though

you will need to edit the file /etc/pacman.d/gnupg/gpg.conf, adding to it a new line:

keyserver pool.sks-keyservers.net

I get the same error using that setting. I tried different arbitrary keyserver domains too and get the same error. Double checked Internet and it's fine still.

can you join the IRC channel? - i do believe that this can be
solved; but tech support is somewhat clumsy on a bug tracker

Hi, the problem is still present. Is there a solution?

its not "still" present - this BR is marked as 'fixed' - it is
present "again"; and i am aware of it - the keyring package needs
to be re-built - i will re-open this ticket though, so that others
may find it easily

the solution is always the same: one of the options described on
the wiki - in this case, it is section #1

https://wiki.parabola.nu/Parabola_Keyring

None of the sections helps, pacman can't refresh the keys. When approximately can this problem be solved? As I understand it, it has been present for a relatively long time, so in fact no one can install the distribution, unless they change the pacman configuration, which is a risk

I checked a few hours ago, well, now there are no problems with the installation, if you follow point 4.6 Verification of package signatures in https://wiki.parabola.nu/Installation_Guide. I'm glad it's all settled.

this was never a critical problem, and it is not "still" present

I don't want to start an argument, but I feel you are being overly dismissive when it comes to that issue.

This problem has been present ever since I've first started using Parabola, which has been at least several years now. Yeah, at the end and I was always able to fix, even if sometimes takes several weeks of just not being able to update any packages, when the --refresh-keys method just refuses to work. It seems to me that anybody that has ever used Parabola had to deal with this issue, probably multiple times, and it's never obvious how to deal with it, especially when you first encounter it. And if you are that much into dealing system administration stuff, it's even harder to deal with. I understand when you are installing and maintaining a Parabola system, you should know what you are generally doing, so it's not for people who have no idea about GNU/Linux system administration, but there are levels of understanding even when it comes to that.

And it's always the same exact key that's the problem.

I feel like you are being way too dismissive about the issue. Honestly, in my years of using Parabola personally, and also helping other people use Parabola, this issue has been the most persistent and most annoying problem of them all. The error message is just too cryptic and doesn't explain what the problem is in a useful way. And I would argue, that in a normal situation, you just should get this error, and yet I get it very frequently.

Please, reconsider the severity of this issue.