Due to an influx of spam, we have had to temporarily disable account registrations. Please write an email to accountsupport@archlinux.org, with your desired username, if you want to get access. Sorry for the inconvenience.
- If you create an additional key, make sure to clear sign the info section using your old one (if still available)
- If you create an additional key, make sure to clear sign the info section using your old one (if still available)
- Import public key into keyring directory: `./keyringctl import --name <username> <(gpg --export <key ID>)`
- Import public key into keyring directory: `./keyringctl import --name <username> <(gpg --export <key ID>)`
-[Create a merge request](https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/merge_requests/new) using the "New Packager Key" template
-[Create a merge request](https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/merge_requests/new) using the "New Packager Key" template
1. Sign packages with the new key only **after one full week** after it has been released to the `[core]` repository (as part of `archlinux-keyring`) with **full trust**. Failing to do so will lead to users having to first upgrade the `archlinux-keyring` package before attempting a system upgrade.
1. Sign packages with the new key only **one full week after** it has been released to the `[core]` repository (as part of `archlinux-keyring`) with **full trust**. Failing to do so will lead to users having to first upgrade the `archlinux-keyring` package before attempting a system upgrade.