With regards to the full output error that is all it says above it just state what key need to be imported and by what it is required. Then about the keyserver I do not know which one it is currently trying to use.
In note number five it states how to import key manually. However, I still have the issue when using yay for the install.It asks for the keys to be imported and the import still fails. I have the option to say no to the import also but i don’t know what that will do.
p.s Do i have to keep the public key I imported as a file around or can it be deleted once it is imported to pacman?
No that seems to harsh. I think I am missing something. I have imported the key already but when using yay it still wants to import the key and it still fails. Although I think I could skip the import in yay since I have already imported the key manually. However, if I do this I am not sure if the keys will get verified.
Yes I have done all the steps in the page. I have run them with sudo since the command prompts you to do so in order for them work.Except figer which doesnt require it. My main issue is if during the yay install I still have to import the keys.
If you install a package from the repositories listed in /etc/pacman.conf then pacman (or yay, or whatever, if you’re using it for installing repo packages) will use the pacman keyring (stored under /etc/pacman.d/gnupg).
If you download a PKGBUILD from the AUR, and it has a signature to validate the download, then makepkg (or yay, or whatever help you’re using) will use your local user’s keyring (stored under $HOME/.gnupg).
This is one reason the Arch wiki mentions it’s important to understand how package management works before using an AUR helper.