From: Lars Ingebrigtsen <larsi@gnus.org>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: 54747@debbugs.gnu.org
Subject: bug#54747: 28.1.50; package.el - Better error message if newer Emacs is required
Date: Sat, 09 Apr 2022 11:47:08 +0200 [thread overview]
Message-ID: <871qy6612b.fsf@gnus.org> (raw)
In-Reply-To: <030e1433-90c0-c0ea-0403-70749e74c2c3@daniel-mendler.de> (Daniel Mendler's message of "Fri, 8 Apr 2022 16:03:54 +0200")
Daniel Mendler <mail@daniel-mendler.de> writes:
> One such "incompat" package where this happens is for example satchel
> from GNU ELPA. Maybe the "incompat" label is incorrect?
I did a `M-x list-packages' in Emacs 28.1, and it doesn't list satchel
as being "incompat" for me. Very odd. Could it be some outdated cached
data somewhere?
> Very well then. I also saw that you added the improved error message if
> a newer Emacs version is required. Thank you! From my side the issue
> about the error message can be closed.
OK; done.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-04-09 9:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 12:16 bug#54747: 28.1.50; package.el - Better error message if newer Emacs is required Daniel Mendler
[not found] ` <handler.54747.B.164924739831028.ack@debbugs.gnu.org>
2022-04-06 12:20 ` bug#54747: Acknowledgement (28.1.50; package.el - Better error message if newer Emacs is required) Daniel Mendler
2022-04-06 12:30 ` Daniel Mendler
2022-04-07 11:46 ` bug#54747: 28.1.50; package.el - Better error message if newer Emacs is required Lars Ingebrigtsen
2022-04-07 11:55 ` Daniel Mendler
2022-04-08 12:51 ` Lars Ingebrigtsen
2022-04-08 14:03 ` Daniel Mendler
2022-04-09 9:47 ` Lars Ingebrigtsen [this message]
2022-04-09 10:13 ` Daniel Mendler
2022-04-07 13:46 ` Rudolf Schlatte
2022-04-08 12:47 ` Lars Ingebrigtsen
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=871qy6612b.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=54747@debbugs.gnu.org \
--cc=mail@daniel-mendler.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 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).