CDN mismatched db signatures #4
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
error: extra-x86-64-v3: signature from "Archlinux CIE Repos (Build 2020/2021) cie@harting.dev" is invalid
error: failed to synchronize all databases (unexpected error)
-> error refreshing databases - exit status 1
Same issue.
Attempted sloutions
None fixed the issue.
Not sure how you jumped to the conclusion its expired, because its certainly not:
What mirror do you use? We got a lot of reports lately that CDN mirror are having problems keeping db/sig in sync. Can you try a non-cdn mirror to confirm?
I jumped to the conclusion it expired because that sounded the most likely reason why a signing key would be invalid. That's also why I made an issue on the alhp-keyring issue tracker instead of anywhere else, because pacman said it was a key problem.
I opened /etc/pacman.d/alhp-mirrorlist in nano and commented out the 2 entries under the "## Worldwide (CDN)" heading and now my pacman -Syu is working again. Guess that was the problem. Thanks.
Not sure its a good idea to close this, I think we should try to solve this instead of recommending switching mirrors. The CDNs probably have a cache purge problem, I'll try to implement a stricter cache purge policy as soon as I find time.
I overhauled the cache purging, lets see how that goes.
GPG key has expired, AUR package out of dateto CDN mismatched db signaturesWell, seems that the new method does not clear correctly either. I now implemented a more "radical" purge method, lets see if that helps.
I implemented cache-tagging, should work fine from now on. Please reopen if the problem persists for you.