Hi David,
I am very sorry. I misjudged the urgency of this topic. I assumed
signing the additional uid is more a "ncie to have", since pacman and
wkd already works fine. I opened the ticket at
https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/143
so we can create the merge requests
On 2022-01-14 16:57:00 (-0800), Brett Cornwall via arch-dev-public wrote:
> On 2022-01-14 21:12, David Runge via arch-dev-public wrote:
> > To all that have added a new @archlinux.org UID or have created a new
> > key, please make sure that all signatures you have received from main
> > signing key
On Fri, Jan 14, 2022 at 04:57:00PM -0800, Brett Cornwall via arch-dev-public
wrote:
> On 2022-01-14 21:12, David Runge via arch-dev-public wrote:
> > To all that have added a new @archlinux.org UID or have created a new
> > key, please make sure that all signatures you have received from main
> >
On Fri, Jan 14, 2022 at 09:12:37PM +0100, David Runge via arch-dev-public wrote:
> If you have gained more than or equal to three main key signatures for
> your new PGP key and the key as well as those signatures are already
> available in the keyring in [core] please rebuild all of your packages
>
On 2022-01-14 21:12, David Runge via arch-dev-public wrote:
To all that have added a new @archlinux.org UID or have created a new
key, please make sure that all signatures you have received from main
signing keys are also present in the current keyring (`pacman-key
--list-sigs @archlinux.org`) or
