From: Daniel Sutton <dan@dpsutton.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: cannot download packages from elpa
Date: Wed, 2 Oct 2019 21:17:23 -0500 [thread overview]
Message-ID: <CAMfzp7YPqKDUN515tzVOqwVh8=eKuGrVpc==gmcydDYPxSmXwg@mail.gmail.com> (raw)
In-Reply-To: <jwvzhiiwq5b.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
It appears so and I see you have helpfully created a package to help out
with that. I'll research how to get our circle builds updated to use the
new keys.
I found a reddit thread you created that is quite helpful as well if anyone
else is in the same boat as me and CIDER:
https://www.reddit.com/r/emacs/comments/bn6k1y/updating_gnu_elpa_keys/
On Wed, Oct 2, 2019 at 8:55 PM Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
> > I've tried to check the normal avenues for status but they are down. I'm
> > confused why https://elpa.gnu.org/packages/ seems to be up but the
> packages
> > are not able to be downloaded. It looks like the tests have been failing
> > due to package resolution for at least 11 days.
>
> 11 days, huh? Sounds like you're bitten by the change of signing keys.
> If you use Emacs-26.3 the problem should disappear.
> If you use an older Emacs to fetch the packages you need to first update
> the keys or disable signature checking.
>
>
> Stefan
>
>
[-- Attachment #2: Type: text/html, Size: 1532 bytes --]
next prev parent reply other threads:[~2019-10-03 2:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 0:44 cannot download packages from elpa Daniel Sutton
2019-10-03 1:55 ` Stefan Monnier
2019-10-03 2:17 ` Daniel Sutton [this message]
2019-10-03 14:19 ` Dmitry Gutov
2019-10-03 3:13 ` dick.r.chiang
2019-10-03 13:16 ` Stefan Monnier
2019-10-03 13:41 ` dick.r.chiang
2019-10-03 14:06 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMfzp7YPqKDUN515tzVOqwVh8=eKuGrVpc==gmcydDYPxSmXwg@mail.gmail.com' \
--to=dan@dpsutton.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.