From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63587@debbugs.gnu.org, emacs@akurth.de
Subject: bug#63587: 29.0.91; package-menu-mark-upgrades does not show available upgrades
Date: Thu, 25 May 2023 20:04:30 +0000 [thread overview]
Message-ID: <871qj4p48h.fsf@posteo.net> (raw)
In-Reply-To: <83wn0wkyk2.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 25 May 2023 22:20:45 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Ping! Philip, are you looking into this?
Sorry, I forgot about it. I'll take a look at this tomorrow or the day
after that. My apologies for the delay.
>> Cc: 63587@debbugs.gnu.org
>> Date: Sun, 21 May 2023 11:01:46 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>>
>> > Date: Fri, 19 May 2023 08:30:46 +0200
>> > From: Andreas Kurth <emacs@akurth.de>
>> >
>> > after setting package-install-upgrade-built-in to a non-nil value, the
>> > command "M-x package-menu-mark-upgrades" won’t show upgradeable non
>> > built-in packages (magit, embark, ...) any more. Same for pressing "U"
>> > in the package menu. Also, the command "M-x list-packages" won’t
>> > announce upgradeable packages in the echo area.
>> >
>> > Setting package-install-upgrade-built-in to nil will revert that
>> > faulty behaviour.
>> >
>> > I bisected the error to commit
>> > ba2c76fa2bc3aabfda7d1d09cc5148f3f9d8e08e in emacs-29 branch.
>>
>> Philip, could you please look into this issue?
next prev parent reply other threads:[~2023-05-25 20:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 6:30 bug#63587: 29.0.91; package-menu-mark-upgrades does not show available upgrades Andreas Kurth
2023-05-21 8:01 ` Eli Zaretskii
2023-05-25 19:20 ` Eli Zaretskii
2023-05-25 20:04 ` Philip Kaludercic [this message]
2023-05-27 8:04 ` Philip Kaludercic
2023-05-27 16:31 ` Andreas Kurth
2023-05-29 11:08 ` Eli Zaretskii
2023-09-06 20:12 ` Stefan Kangas
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=871qj4p48h.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=63587@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=emacs@akurth.de \
/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.