From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Corwin Brust <corwin@bru.st>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
54117@debbugs.gnu.org, 54117-done@debbugs.gnu.org
Subject: bug#54117: 28.0.91; Upgrading packages not working
Date: Thu, 14 Apr 2022 08:47:32 +0800 [thread overview]
Message-ID: <87h76wtrrv.fsf@yahoo.com> (raw)
In-Reply-To: <CAJf-WoQ=p+QG3XkrLhOQ-E58TsrGgZxefvd1CY3aSP6aZZg51w@mail.gmail.com> (Corwin Brust's message of "Wed, 13 Apr 2022 10:13:30 -0500")
Corwin Brust <corwin@bru.st> writes:
>> Po Lu <luangruo@yahoo.com> writes:
>>
>> > In fact, nothing gets marked for upgrades, and I have got quite some
>> > more packages installed, so I suspect some problem in the upgrade
>> > marking process.
>>
>> I got around to looking at this: every package installed is labeled as
>> "external" instead of "installed". Since I don't know what the
>> difference between the two is, I installed a change to also mark
>> upgradable "external" packages, and am closing this bug.
>>
>
> Did this change go to the release branch (for the future 28.2) or to
> the trunk or both?
Just to master. It didn't seem safe enough for the release branch,
since it isn't a regression in 28.1.
next prev parent reply other threads:[~2022-04-14 0:47 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h76wtrrv.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=54117-done@debbugs.gnu.org \
--cc=54117@debbugs.gnu.org \
--cc=corwin@bru.st \
--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 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.