Arch Linux User Repository

@anelgarhy You shouldn't be signing source artifacts with your key as you are not the upstream maintainer. Nothing that's tracked in this repo needs to have separate source signature files (you can sign your Git commits if you like) and the upstream artifacts should have checksums, but they should only have trusted keys if upstream publishes signed artifacts.

Also don't conflict with jolt-bin, just jolt. It will resolve it from there. All package variants should conflict with the base package but not between each other or from the base to variants.

@dividebysandwich after talking to my Arch maintainer friend turned out that makepkg doesn't automatically fetch the GPG key, and it was working for me because I do already have the key in my keystore.

So I have to make the choose to either remove the signature from my packages or just require anyone to do one additional step and import my key so they have a ~pinky promise~ from me that i did in fact read that code

@anelgarhy Weird, I did try both openpgp and ubuntu in the config but neither seemed to work. I ran the manual import and that did the trick, thanks!

@dividebysandwich: my key should be uploaded on keys.openpgp.org and keyserver.ubuntu.com, am not sure why it wasn't able to fetch it. You can try to import it manualy for now, until I figure out the issue

gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys EF4B4CB5DFB8822216A473B1597AB12E66262898

thanks for reporting

I keep getting an error that there is no public key, and I already changed key servers.