From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 24467@debbugs.gnu.org, SK Kim <tttuuu888@gmail.com>,
Stefan Monnier <monnier@IRO.UMontreal.CA>,
21703@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#24467: bug#21703: adding package archives after calling package-initialize lists all their packages as "new"
Date: Tue, 17 Aug 2021 14:39:29 +0200 [thread overview]
Message-ID: <87wnok5jpa.fsf@web.de> (raw)
In-Reply-To: <87o89xd18f.fsf_-_@gnus.org> (Lars Ingebrigtsen's message of "Mon, 16 Aug 2021 14:26:40 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>
> >> It's clearly a bug, and it's made worse in Emacs-27 where
> >> package-initialize is called automatically before reading ~/.emacs.
> >> IOW, I think "this" needs to be fixed before Emacs-27.1.
> >
> > I just installed a patch which should reduce the impact of this problem
> > in Emacs-27.1: the problem still occurs if you setq package-archives
> > after calling package-initialize, but at least you can now setq
> > package-archives in your ~/.emacs rather than having to do it in your
> > early-init.el.
>
> Is there more to be done here, or is this a sufficient solution to the
> issue?
If nothing more was changed, then the originally reported problem is not
fixed. That behavior might still annoy or confuse people then.
Michael.
prev parent reply other threads:[~2021-08-17 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 5:29 bug#24467: 25.1; package SK Kim
2016-09-19 22:01 ` Noam Postavsky
2016-09-24 22:28 ` Michael Heerdegen
2016-09-25 2:45 ` npostavs
2016-09-25 13:38 ` Michael Heerdegen
2018-11-03 15:07 ` Stefan Monnier
2019-01-22 22:56 ` Stefan Monnier
2021-08-16 12:26 ` bug#21703: adding package archives after calling package-initialize lists all their packages as "new" Lars Ingebrigtsen
2021-08-17 12:39 ` Michael Heerdegen [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=87wnok5jpa.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=21703@debbugs.gnu.org \
--cc=24467@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=npostavs@users.sourceforge.net \
--cc=tttuuu888@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.
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.