From: Dmitry Gutov <dmitry@gutov.dev>
To: Ihor Radchenko <yantar92@posteo.net>,
Philip Kaludercic <philipk@posteo.net>
Cc: 63800@debbugs.gnu.org
Subject: bug#63800: 30.0.50; [ELPA] Inaccurate installation instructions for built-in packages
Date: Thu, 15 Jun 2023 05:08:41 +0300 [thread overview]
Message-ID: <ee60fc2a-3c7d-094e-6a7b-3b5e6aacbd6b@gutov.dev> (raw)
In-Reply-To: <875y89t2a1.fsf@localhost>
On 31/05/2023 09:59, Ihor Radchenko wrote:
> Philip Kaludercic<philipk@posteo.net> writes:
>
>>> However, this command will fail for built-in packages. This is
>>> particularly a problem for older (<29) Emacs versions.
>> You probably want to set `package-install-upgrade-built-in' to non-nil,
>> or use the package menu to install packages.
> Sure. But only in Emacs >=29 and it is not mentioned on the ELPA page.
> For Emacs <29 ELPA instruction simply does not work - attempting to
> follow it will just produce unhelpful message that package is already
> installed.
Is that a problem with the command or with the expectations?
When Org is built-in, it *is* already installed, isn't it?
You will also see the same message if you try to use 'M-x
package-install' as a means to upgrade any other already-installed
package, whether it is built-in or not.
next prev parent reply other threads:[~2023-06-15 2:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 8:05 bug#63800: 30.0.50; [ELPA] Inaccurate installation instructions for built-in packages Ihor Radchenko
2023-05-31 6:46 ` Philip Kaludercic
2023-05-31 6:59 ` Ihor Radchenko
2023-06-07 19:06 ` Philip Kaludercic
2023-06-08 11:01 ` Ihor Radchenko
2023-06-15 2:08 ` Dmitry Gutov [this message]
2023-06-15 6:04 ` Ihor Radchenko
2023-06-15 12:34 ` Dmitry Gutov
2023-06-15 15:35 ` Philip Kaludercic
2023-06-15 20:56 ` Ihor Radchenko
2023-07-09 11:59 ` Ihor Radchenko
2023-07-10 2:14 ` Dmitry Gutov
2023-07-12 7:46 ` Philip Kaludercic
2023-07-12 16:24 ` Ihor Radchenko
2023-07-12 16:38 ` Philip Kaludercic
2023-07-13 9:39 ` Ihor Radchenko
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=ee60fc2a-3c7d-094e-6a7b-3b5e6aacbd6b@gutov.dev \
--to=dmitry@gutov.dev \
--cc=63800@debbugs.gnu.org \
--cc=philipk@posteo.net \
--cc=yantar92@posteo.net \
/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).