Menu
Recently tried to update emacs packages and got this.
Failed to verify signature archive-contents.sig: No public key for 066DAFCB81E42C40 created at 2019-10-02T10:10:02+0100 using RSA Command output: gpg: Signature made Wed 02 Oct 2019 10:10:02 AM BST gpg: using RSA key C433554766D3DDC64221BFAA066DAFCB81E42C40 gpg: Can't check signature: No public key Any ideas why?
243
This is not an error caused by misconfiguration but is due to the change of the file package-keyring.gpg from Emacs 26.3. As stated from the release note: New GPG key for GNU ELPA package signature checking.
If your keys are already too old, causing signature verification errors when installing packages, then in order to install this package you can do the following: Modify the expiration date of the old key, e.g. with something like: temporarily disable signature verification (see variable `package-check-signature').
Looks like a bug in your version of Emacs. You can probably circumvent it by setting package-check-signature to nil. Show activity on this post. This is not an error caused by misconfiguration but is due to the change of the file package-keyring.gpg from Emacs 26.3.
The signature check failed because you don't have the new key (the old signature key expired on Sep 23). The new key is available from the usual GPG key-servers, comes with Emacs≥26.3, and can also be obtained by installing the package gnu-elpa-keyring-update.
See https://emacs.stackexchange.com/questions/233/ for the same question.
The signature check failed because you don't have the new key (the old signature key expired on Sep 23). The new key is available from the usual GPG key-servers, comes with Emacs≥26.3, and can also be obtained by installing the package gnu-elpa-keyring-update.
117
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
