[arch-general] Package signature error after updated GPG key

Filipe Laíns filipe.lains at gmail.com
Wed Jul 8 19:35:12 UTC 2020


On Wed, 2020-07-08 at 21:21 +0200, NicoHood wrote:
> I am not sure if I understood correct. I've simply refreshed the gpg key
> (and the subkey) which was included into the new keyring. The package
> that causes trouble is older than that change. Since makepkg refers to
> package building, I think this does not help here. I expect that I do
> not need to rebuild all packages just because the GPG key was renewed.
> 
> Is it more clear now?
> 
Ah, then the user has an outdated keyring or a corrupted file.

Refreshing the keys should have no impact, what would have an impact
would be creating a new key, which is what I assumed happened.

Filipe Laíns
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <https://lists.archlinux.org/pipermail/arch-general/attachments/20200708/9bc0e600/attachment.sig>


More information about the arch-general mailing list