Gpg key error while trying to install org-roam

Failed to verify signature archive-contents.sig:
No public key for 645357D2883A0966 created at 2025-01-26T04:05:02+0600 using EDDSA
Command output:
gpg: Signature made Sun 26 Jan 2025 04:05:02 AM +06
gpg: using EDDSA key 0327BE68D64D9A1A66859F15645357D2883A0966
gpg: Can’t check signature: No public key

I really want to try using org-roam but simply cannot install it. Specially this error is something I’m seeing a lot. I got this one from trying to install a package from M-x package-install
I am very new to emacs and org mode and want to get into org roam. Can anyone tell me how can I fix this please? And maybe a link from where I can learn to install org-roam?

Probably this will help. (setq package-check-signature nil)

1 Like

Disabling the signature should work,

but somehow your public keys got messed up.

Make sure you have gnupg installed in your os, then delete your .emacs.d/elpa folder and reinstall any packages you have had installed. Before installing anything, emacs should download the keys and put them in .emacs.d/elpa/gnupg/pubring.kbx this public keyring is possibly missing from your system.

so, I don’t have a folder .emacs.d. The folder wasn’t created automatically while installing emacs. I do have a .config/emacs folder with these things, ~/.c/emacs > ls
bin docs early-init.el LICENSE lisp modules profiles README.md shell.nix static

So, yeah I guess something is missing here. Should I reinstall emacs?

Worked :smiley:
Btw, is it okay to keep it nil? I mean everything seems to work fine now

No. Your flavour of Emacs might do things differently. I use vanilla Emacs and without any configuration it does things one way, but other distributions might prefer to do things differently. No need to reinstall.

Sure, enjoy for now. Signatures are a way to check if things were tampered. But the security risk in Emacs is very minimal, so no need to worry about them right now I feel, you can keep it nil. It is a reasonable thing to do in the short run.