GNU bug report logs -
#38494
25.2.2 gpg error upon listing packages; auctex not located in repos
Previous Next
Reported by: Stuart Little <achirvasub <at> gmail.com>
Date: Wed, 4 Dec 2019 21:02:02 UTC
Severity: normal
Tags: confirmed
Found in version 25.2.2
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 38494 in the body.
You can then email your comments to 38494 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#38494
; Package
emacs
.
(Wed, 04 Dec 2019 21:02:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Stuart Little <achirvasub <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Wed, 04 Dec 2019 21:02:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
I'm running Ubuntu 18.04.3 LTS, with that distro's standard emacs distribution, 25.2.2.
Problem: running
M-x package-list-packages
results in a gpg error:
--- cut here ---
Failed to verify signature archive-contents.sig:
No public key for 066DAFCB81E42C40 created at 2019-12-02T18:00:02-0500 using RSA
Command output:
gpg: Signature made Mon 02 Dec 2019 06:00:02 PM EST
gpg: using RSA key C433554766D3DDC64221BFAA066DAFCB81E42C40
gpg: Can't check signature: No public key
--- done ---
I believe this might be the reason why the package listing then fails to display auctex. I can find other, auctex-related packages, e.g.
auctex-latexmk 20170618.1636 incompat melpa Add LatexMk support to AUCTeX
They are nevertheless marked 'incompat' and clicking one (the one above for instance) results in a notification as below:
--- cut here ---
Status: Incompatible because it depends on uninstallable packages.
Archive: melpa
Version: 20170618.1636
Summary: Add LatexMk support to AUCTeX
Requires: auctex-11.87 (not available)
Homepage: https://github.com/tom-tan/auctex-latexmk/
Keywords: [tex]
--- done ---
My package repo section in .emacs reads
--- cut here ---
;; emacs package repositories
(require 'package)
(setq package-archives '(("ELPA" . "http://tromey.com/elpa/")
("gnu" . "http://elpa.gnu.org/packages/")
;;("marmalade" . "http://marmalade-repo.org/packages/")
("melpa" . "http://melpa.milkbox.net/packages/")))
;; adds repository for org mode
(require 'package)
(add-to-list 'package-archives '("org" . "http://orgmode.org/elpa/") t)
(package-initialize)
--- done ---
On a different system I got around this by compiling the nweest emacs from source[0], but it would be good to figure out what's going on. I've had this happen on other systems running pre-26 emacsen.
---
References:
[0] https://savannah.gnu.org/git/?group=emacs
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#38494
; Package
emacs
.
(Sun, 02 Aug 2020 10:15:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 38494 <at> debbugs.gnu.org (full text, mbox):
Stuart Little <achirvasub <at> gmail.com> writes:
> I'm running Ubuntu 18.04.3 LTS, with that distro's standard emacs distribution, 25.2.2.
>
> Problem: running
>
> M-x package-list-packages
>
> results in a gpg error:
>
> --- cut here ---
>
> Failed to verify signature archive-contents.sig:
> No public key for 066DAFCB81E42C40 created at 2019-12-02T18:00:02-0500 using RSA
> Command output:
> gpg: Signature made Mon 02 Dec 2019 06:00:02 PM EST
> gpg: using RSA key C433554766D3DDC64221BFAA066DAFCB81E42C40
> gpg: Can't check signature: No public key
>
> --- done ---
I can reproduce this on an 18.04 LTS. emacs -Q:
Failed to verify signature archive-contents.sig:
No public key for 066DAFCB81E42C40 created at 2020-08-02T09:05:02+0000 using RS\
A
Command output:
gpg: Signature made Sun Aug 2 09:05:02 2020 UTC
gpg: using RSA key C433554766D3DDC64221BFAA066DAFCB81E42C40
gpg: Can't check signature: No public key
But I vaguely recall that there was something about an expiring key that
made things not work? In that case, there isn't much to be done here.
Does anybody remember?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Added tag(s) confirmed.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Sun, 02 Aug 2020 10:15:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#38494
; Package
emacs
.
(Sun, 02 Aug 2020 10:51:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 38494 <at> debbugs.gnu.org (full text, mbox):
For what it's worth, this has been broken on Ubuntu 18.04 for just about ever.. On all of my Ubuntu machines I simply build the emacs-27 branch from source[0].
It's been working fine for months (I forget when the problem first manifested).
---
References:
[0] https://savannah.gnu.org/git/?group=emacs
On August 2, 2020 6:14:10 AM EDT, Lars Ingebrigtsen <larsi <at> gnus.org> wrote:
>Stuart Little <achirvasub <at> gmail.com> writes:
>
>> I'm running Ubuntu 18.04.3 LTS, with that distro's standard emacs
>distribution, 25.2.2.
>>
>> Problem: running
>>
>> M-x package-list-packages
>>
>> results in a gpg error:
>>
>> --- cut here ---
>>
>> Failed to verify signature archive-contents.sig:
>> No public key for 066DAFCB81E42C40 created at
>2019-12-02T18:00:02-0500 using RSA
>> Command output:
>> gpg: Signature made Mon 02 Dec 2019 06:00:02 PM EST
>> gpg: using RSA key
>C433554766D3DDC64221BFAA066DAFCB81E42C40
>> gpg: Can't check signature: No public key
>>
>> --- done ---
>
>I can reproduce this on an 18.04 LTS. emacs -Q:
>
>Failed to verify signature archive-contents.sig:
>No public key for 066DAFCB81E42C40 created at 2020-08-02T09:05:02+0000
>using RS\
>A
>Command output:
>gpg: Signature made Sun Aug 2 09:05:02 2020 UTC
>gpg: using RSA key
>C433554766D3DDC64221BFAA066DAFCB81E42C40
>gpg: Can't check signature: No public key
>
>But I vaguely recall that there was something about an expiring key
>that
>made things not work? In that case, there isn't much to be done here.
>
>Does anybody remember?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#38494
; Package
emacs
.
(Sun, 02 Aug 2020 10:58:02 GMT)
Full text and
rfc822 format available.
Message #16 received at 38494 <at> debbugs.gnu.org (full text, mbox):
Lars Ingebrigtsen <larsi <at> gnus.org> writes:
> But I vaguely recall that there was something about an expiring key that
> made things not work? In that case, there isn't much to be done here.
>
> Does anybody remember?
Yup:
https://metaredux.com/posts/2019/12/09/dealing-with-expired-elpa-gpg-keys.html
So I don't think there's anything to be done in this bug report, and I'm
closing it.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
bug closed, send any further explanations to
38494 <at> debbugs.gnu.org and Stuart Little <achirvasub <at> gmail.com>
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Sun, 02 Aug 2020 10:58:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 30 Aug 2020 11:24:07 GMT)
Full text and
rfc822 format available.
This bug report was last modified 3 years and 234 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.