unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* can't connect to ELPA any more
@ 2024-06-30  8:47 Uwe Brauer via Emacs development discussions.
  2024-06-30  9:23 ` Eli Zaretskii
  2024-07-03 22:07 ` Mekeor Melire
  0 siblings, 2 replies; 8+ messages in thread
From: Uwe Brauer via Emacs development discussions. @ 2024-06-30  8:47 UTC (permalink / raw)
  To: emacs-devel

Hi

I just realized when I run 

Package-list-packages


MELPA, gnu and non-gnu packages are displayed but elpa not anymore.

The error is 
--8<---------------cut here---------------start------------->8---
Entering debugger...
package--check-signature-content: Failed to verify signature: "archive-contents.sig"
Mark set [3 times]
Importing package-keyring.gpg...done
package--check-signature-content: Failed to verify signature: "archive-contents.sig" [2 times]
Package refresh done
Packages that can be upgraded: 352;
--8<---------------cut here---------------end--------------->8---


How can I obtain a correct signature?
I have never seen that error before

Regards


Uwe Brauer 



-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 





^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: can't connect to ELPA any more
  2024-06-30  8:47 can't connect to ELPA any more Uwe Brauer via Emacs development discussions.
@ 2024-06-30  9:23 ` Eli Zaretskii
  2024-06-30 10:12   ` Philip Kaludercic
  2024-07-03 22:07 ` Mekeor Melire
  1 sibling, 1 reply; 8+ messages in thread
From: Eli Zaretskii @ 2024-06-30  9:23 UTC (permalink / raw)
  To: Uwe Brauer, Stefan Monnier, Philip Kaludercic; +Cc: emacs-devel

Here's what I get from package-list-packages in "emacs -Q" (in the
*Error* buffer):

  Failed to verify signature archive-contents.sig:
  Bad signature from 645357D2883A0966 GNU ELPA Signing Agent (2023) <elpasign@elpa.gnu.org>
  Command output:
  gpg: Signature made 30/06/2024 12:10:02 Jerusalem Daylight Time
  gpg:                using EDDSA key 0327BE68D64D9A1A66859F15645357D2883A0966
  gpg: BAD signature from "GNU ELPA Signing Agent (2023) <elpasign@elpa.gnu.org>" [unknown]

Stefan, Philip: could you please look into this?



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: can't connect to ELPA any more
  2024-06-30  9:23 ` Eli Zaretskii
@ 2024-06-30 10:12   ` Philip Kaludercic
  2024-06-30 10:30     ` Uwe Brauer
                       ` (2 more replies)
  0 siblings, 3 replies; 8+ messages in thread
From: Philip Kaludercic @ 2024-06-30 10:12 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: Uwe Brauer, Stefan Monnier, emacs-devel

Eli Zaretskii <eliz@gnu.org> writes:

> Here's what I get from package-list-packages in "emacs -Q" (in the
> *Error* buffer):
>
>   Failed to verify signature archive-contents.sig:
>   Bad signature from 645357D2883A0966 GNU ELPA Signing Agent (2023) <elpasign@elpa.gnu.org>
>   Command output:
>   gpg: Signature made 30/06/2024 12:10:02 Jerusalem Daylight Time
>   gpg:                using EDDSA key 0327BE68D64D9A1A66859F15645357D2883A0966
>   gpg: BAD signature from "GNU ELPA Signing Agent (2023) <elpasign@elpa.gnu.org>" [unknown]
>
> Stefan, Philip: could you please look into this?

I believe you can fix this by installing "gnu-elpa-keyring-update".

-- 
	Philip Kaludercic on peregrine



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: can't connect to ELPA any more
  2024-06-30 10:12   ` Philip Kaludercic
@ 2024-06-30 10:30     ` Uwe Brauer
  2024-06-30 10:30     ` Eli Zaretskii
  2024-07-01  1:32     ` Michael Heerdegen via Emacs development discussions.
  2 siblings, 0 replies; 8+ messages in thread
From: Uwe Brauer @ 2024-06-30 10:30 UTC (permalink / raw)
  To: Philip Kaludercic; +Cc: Eli Zaretskii, Uwe Brauer, Stefan Monnier, emacs-devel

[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]

>>> "PK" == Philip Kaludercic <philipk@posteo.net> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>> Here's what I get from package-list-packages in "emacs -Q" (in the
>> *Error* buffer):
>> 
>> Failed to verify signature archive-contents.sig:
>> Bad signature from 645357D2883A0966 GNU ELPA Signing Agent (2023) <elpasign@elpa.gnu.org>
>> Command output:
>> gpg: Signature made 30/06/2024 12:10:02 Jerusalem Daylight Time
>> gpg:                using EDDSA key 0327BE68D64D9A1A66859F15645357D2883A0966
>> gpg: BAD signature from "GNU ELPA Signing Agent (2023) <elpasign@elpa.gnu.org>" [unknown]
>> 
>> Stefan, Philip: could you please look into this?

> I believe you can fix this by installing "gnu-elpa-keyring-update".


Well then I obtain 

Contacting host: elpa.gnu.org:443
package--with-response-buffer-1: https://elpa.gnu.org/packages/gnu-elpa-keyring-update-2022.12.tar: Not found
Updating buffer list...done


Catch 22?


-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: can't connect to ELPA any more
  2024-06-30 10:12   ` Philip Kaludercic
  2024-06-30 10:30     ` Uwe Brauer
@ 2024-06-30 10:30     ` Eli Zaretskii
  2024-07-01  1:32     ` Michael Heerdegen via Emacs development discussions.
  2 siblings, 0 replies; 8+ messages in thread
From: Eli Zaretskii @ 2024-06-30 10:30 UTC (permalink / raw)
  To: Philip Kaludercic; +Cc: oub, monnier, emacs-devel

> From: Philip Kaludercic <philipk@posteo.net>
> Cc: Uwe Brauer <oub@mat.ucm.es>,  Stefan Monnier <monnier@iro.umontreal.ca>,
>   emacs-devel@gnu.org
> Date: Sun, 30 Jun 2024 10:12:34 +0000
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Here's what I get from package-list-packages in "emacs -Q" (in the
> > *Error* buffer):
> >
> >   Failed to verify signature archive-contents.sig:
> >   Bad signature from 645357D2883A0966 GNU ELPA Signing Agent (2023) <elpasign@elpa.gnu.org>
> >   Command output:
> >   gpg: Signature made 30/06/2024 12:10:02 Jerusalem Daylight Time
> >   gpg:                using EDDSA key 0327BE68D64D9A1A66859F15645357D2883A0966
> >   gpg: BAD signature from "GNU ELPA Signing Agent (2023) <elpasign@elpa.gnu.org>" [unknown]
> >
> > Stefan, Philip: could you please look into this?
> 
> I believe you can fix this by installing "gnu-elpa-keyring-update".

How come this is suddenly required?  It's a nuisance to keep this
updated at all times.  I think I'd rather disable signature
verification.  Too bad.



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: can't connect to ELPA any more
  2024-06-30 10:12   ` Philip Kaludercic
  2024-06-30 10:30     ` Uwe Brauer
  2024-06-30 10:30     ` Eli Zaretskii
@ 2024-07-01  1:32     ` Michael Heerdegen via Emacs development discussions.
  2024-07-01 11:23       ` Eli Zaretskii
  2 siblings, 1 reply; 8+ messages in thread
From: Michael Heerdegen via Emacs development discussions. @ 2024-07-01  1:32 UTC (permalink / raw)
  To: emacs-devel

Philip Kaludercic <philipk@posteo.net> writes:

> I believe you can fix this by installing "gnu-elpa-keyring-update".

I do have installed this packages for a while; nonetheless did I get
this (or a very similar) error yesterday.  But _only_ yesterday, not on
any other day in the past couple of weeks.  And also not now.  So it may
be an intermediate problem.

Michael.




^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: can't connect to ELPA any more
  2024-07-01  1:32     ` Michael Heerdegen via Emacs development discussions.
@ 2024-07-01 11:23       ` Eli Zaretskii
  0 siblings, 0 replies; 8+ messages in thread
From: Eli Zaretskii @ 2024-07-01 11:23 UTC (permalink / raw)
  To: Michael Heerdegen; +Cc: emacs-devel

> Date: Mon, 01 Jul 2024 03:32:46 +0200
> From:  Michael Heerdegen via "Emacs development discussions." <emacs-devel@gnu.org>
> 
> Philip Kaludercic <philipk@posteo.net> writes:
> 
> > I believe you can fix this by installing "gnu-elpa-keyring-update".
> 
> I do have installed this packages for a while; nonetheless did I get
> this (or a very similar) error yesterday.  But _only_ yesterday, not on
> any other day in the past couple of weeks.  And also not now.  So it may
> be an intermediate problem.

Not here, I still see the same error message and the text in the
buffer I posted earlier.  Annoying.



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: can't connect to ELPA any more
  2024-06-30  8:47 can't connect to ELPA any more Uwe Brauer via Emacs development discussions.
  2024-06-30  9:23 ` Eli Zaretskii
@ 2024-07-03 22:07 ` Mekeor Melire
  1 sibling, 0 replies; 8+ messages in thread
From: Mekeor Melire @ 2024-07-03 22:07 UTC (permalink / raw)
  To: emacs-devel

Is this related? "failure in installing xelb: ELPA signature
verification failure", 22 Apr 2024, help-gnu-emacs mailing-list:

https://lists.gnu.org/archive/html/help-gnu-emacs/2024-04/msg00210.html



^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2024-07-03 22:07 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-06-30  8:47 can't connect to ELPA any more Uwe Brauer via Emacs development discussions.
2024-06-30  9:23 ` Eli Zaretskii
2024-06-30 10:12   ` Philip Kaludercic
2024-06-30 10:30     ` Uwe Brauer
2024-06-30 10:30     ` Eli Zaretskii
2024-07-01  1:32     ` Michael Heerdegen via Emacs development discussions.
2024-07-01 11:23       ` Eli Zaretskii
2024-07-03 22:07 ` Mekeor Melire

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).