Thanks for the help. Build started, but came to an end with
logrotate ... Passed
==> Verifying source file signatures with gpg…
nginx-1.18.0.tar.gz … FAILED (unknown public key 520A9993A1C052F8)
==> ERROR: One or more PGP signatures could not be verified!
Failed to build nginx-rtmp
yay -S nginx-rtmp --editmenu --mflags "--skipchecksums --skippgpcheck"
Then edit the arch field, as per @Darksky’s suggestions.
Incidentally, I’ve co-maintained a couple of packages with TheGoliath on AUR. He has an aarch64 system and maintains a couple of multi-arch packages. If you are able to successfully build the package with the above command then I’d advise leaving an AUR comment. He’ll probably make the package multi-arch to simplify future installation/upgrades.
Thanks for the help, but still no luck. Using the yay command, the build comes to an end with a signature related error message, no matter if I choose to import the keys or not.
e.g.:
:: PGP keys need importing:
→ B0F4253373F8F6F510D42178520A9993A1C052F8, required by: nginx-rtmp
==> Import? [Y/n] y
:: Importing keys with gpg…
gpg: keyserver receive failed: General error
problem importing keys
This looks pretty much the same as the output of Package Manager, which I was using before.
Maybe it is better to try to import the missing keys. First I’ll check if the missing keys are still valid. If so, I will try to import them.
Went to the project page and saw in the comments, that other users were suspecting that there is something wrong with the keys. So I tried to find out how to install from AUR manually. Which is actually very simple. So I did: