all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: dick.r.chiang@gmail.com
Cc: emacs-devel@gnu.org
Subject: Re: cannot download packages from elpa
Date: Thu, 03 Oct 2019 10:06:11 -0400	[thread overview]
Message-ID: <jwv7e5mvt0y.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87sgoaaqua.fsf@dick> (dick r. chiang's message of "Thu, 03 Oct 2019 09:41:49 -0400")

> Is key expiration not par for the course?  It's not clear what could have been
> done differently.

I hope we'll have an answer to that before the next expiration (in 2024).
For me, it's something like:

- arrange for gnu-elpa-keyring-update to be pre-installed (and if
  needed, extra tricks in package.el to encourage the user to update it
  when it's out of date).  So at least any user using M-x package-refresh
  would get a chance at discovering that there's an update pending.

- Create new keys more frequently (e.g. I plan at rolling out a new
  signing key in 2 years or so) so by the time a key expires, your Emacs
  already came with a newer key if it's recentish (compared to the new
  key only appearing in Emacs-26.3, less than a month before the
  previous key expired).

> The tragedies are emacs's outmoded packaging tools, and

Being myself outmoded I don't know what is outmoded about package.el.

Unless by "outmoded" you mean "makes efforts to protect privacy", in
which case I do see what you mean, such as the fact that Emacs
doesn't automatically check for updates by contacting some server
every time you launch it.

On this front, I've been thinking that maybe we could try some steps in
the "less outmoded" direction along the lines of:
- keep track of the last time we refreshed the local copy of the
  archive-contents metadata.
- if it's older than N months, upon startup, emit a message
  encouraging/reminding the user to refresh it.
Along the same lines, when the local copy of the archive-contents
metadata indicates that one of your packages is out of date, we could
emit a message encouraging/reminding the user to upgrade it.

> elpa's inscrutability.

Not sure if you're talking about ELPA the infrastructure/protocol or
about GNU ELPA in particular, but in either case, I'll be more than
happy to try to explain, especially if that can lead to someone helping
me out with GNU ELPA, where I feel much too often quite lonely
(additionally to feeling inadequate because it's really not my area of
expertise).


        Stefan




      reply	other threads:[~2019-10-03 14:06 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
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 [this message]

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=jwv7e5mvt0y.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=dick.r.chiang@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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.