From: Pierre Rouleau <prouleau001@gmail.com>
To: Micha Silver <tsvibar@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, help-gnu-emacs@gnu.org
Subject: Re: Failure getting compat on Emacs <29. seq.2.24 signature expired in gnu elpa?
Date: Mon, 3 Jun 2024 09:38:50 -0400 [thread overview]
Message-ID: <CALTqLiY0c3v2EVJ-ks5jRrMm93yKYJDKcqX45o1PRhpf8+dw1g@mail.gmail.com> (raw)
In-Reply-To: <b1a03e35-4c23-4de4-8850-8d21f45fcc08@gmail.com>
On Mon, Jun 3, 2024 at 8:02 AM Micha Silver <tsvibar@gmail.com> wrote:
>
> On 03/06/2024 14:55, Pierre Rouleau wrote:
> > On Mon, Jun 3, 2024 at 12:59 AM Stefan Monnier via Users list for the GNU
> > Emacs text editor <help-gnu-emacs@gnu.org> wrote:
>
> >
> > On that older system with Emacs 26.3 where the failure occurs,
> > I tried to install the `gnu-elpa`keyring-update` package but that
> failed.
> > I tried with `package-check-signature' set to allow-unsigned and
> > also tried with it set to nil. In both case it failed with the following
> > message:
> >
> > Contacting host: elpa.gnu.org:443
> >
> > Install package ‘gnu-elpa-keyring-update-2022.12’? (y or n) y
> > Contacting host: elpa.gnu.org:443
> > package-install-from-archive:
> > https://elpa.gnu.org/packages/gnu-elpa-keyring-update-2022.12.tar: Not
> found
> >
> > How would I extend the lifetime of the 2019 key?
>
>
> (total newbie here) I downloaded the 2022 package manually, then ran
>
> M-x package-install-file
>
> Thanks Micha for reminding me about the package-install-file!
Installing the file using (package-install-file
"gnu-elpa-keyring-update-pkg.el")
does create the elpa directory with the .el fles and byte-compiles it but
it does
not place the etc sub-directory and does not create the
gnu-elpa-keyring-update-2022.12.1.signed file in the elpa directory.
- To handle the etc directory, I just copied it
- As far as the missing gnu-elpa-keyring-update-2022.12.1.signed file I
tried without it
and then tried with a copy of that file.
The problem with gnu elpa was solved. However I still had a http 404
problem if nongnu,
("nongnu" . "https://elpa.nongnu.org/nongnu") ,
was included inside the the `package-archives`:
with `M-x package-list-packages`
error in process filter: Error retrieving:
https://elpa.nongnu.org/nongnuarchive-contents (error http 404)
The *problem was the missing trailing slash in the URL string*!
The problem was inside my init.el file.
Would it make sense to include a function that would add cons cells in
package-archives and would check for missing trailing slash?
That function could also deal with various issues that occurred over time
like the one for emacs 26.1 and 26.2 having to set
gnutls-algorithm-priority?
Thanks Stephan & Micha!
--
/Pierre
next prev parent reply other threads:[~2024-06-03 13:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-02 17:57 Failure getting compat on Emacs <29. seq.2.24 signature expired in gnu elpa? Pierre Rouleau
2024-06-03 4:58 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-06-03 11:55 ` Pierre Rouleau
[not found] ` <b1a03e35-4c23-4de4-8850-8d21f45fcc08@gmail.com>
2024-06-03 13:38 ` Pierre Rouleau [this message]
2024-06-03 13:54 ` Robert Pluim
2024-06-03 13:57 ` Pierre Rouleau
2024-06-03 14:48 ` Stefan Monnier
2024-06-03 21:51 ` Pierre Rouleau
2024-06-04 1:50 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALTqLiY0c3v2EVJ-ks5jRrMm93yKYJDKcqX45o1PRhpf8+dw1g@mail.gmail.com \
--to=prouleau001@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=tsvibar@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).