From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 54117@debbugs.gnu.org
Subject: bug#54117: 28.0.91; Upgrading packages not working
Date: Wed, 23 Feb 2022 18:45:16 +0800 [thread overview]
Message-ID: <87wnhl9803.fsf@yahoo.com> (raw)
In-Reply-To: <878ru1an5k.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 23 Feb 2022 11:32:39 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Po Lu <luangruo@yahoo.com> writes:
>
>> Install some packages from NonGNU ELPA and wait for newer versions to
>> become available. Then, type U in the package list. Those packages
>> will not be marked for upgrades. (I hope I'm not doing anything wrong
>> here.)
>
> I tried `U' in the package list and it said
>
> ---
> Packages marked for upgrading: 18
> ---
>
> So it seems like it's working for me.
Hmm, which packages? I have geiser stuck on 0.22 (while 0.22.2 shows up
in the package list), to name one example.
Thanks.
next prev parent reply other threads:[~2022-02-23 10:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <878ru29vqj.fsf.ref@yahoo.com>
2022-02-23 2:12 ` bug#54117: 28.0.91; Upgrading packages not working Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-23 10:32 ` Lars Ingebrigtsen
2022-02-23 10:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-02-23 10:54 ` Lars Ingebrigtsen
2022-02-23 11:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-13 7:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-13 15:13 ` Corwin Brust
2022-04-14 0:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-14 14:20 ` Corwin Brust
2022-04-25 11:33 ` Dmitry Gutov
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=87wnhl9803.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=54117@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.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 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).