From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: 71356@debbugs.gnu.org, philipk@posteo.net, acorallo@gnu.org
Subject: bug#71356: use-package doesn't load org from elpa
Date: Thu, 06 Jun 2024 09:02:28 +0300 [thread overview]
Message-ID: <86ed9aip6z.fsf@gnu.org> (raw)
In-Reply-To: <CAO48Bk-y=QYVbY56-RTCc-nh0KWP3Sh-8a_Yjb4j=v0-EdO2KQ@mail.gmail.com> (message from Pedro Andres Aranda Gutierrez on Thu, 6 Jun 2024 07:46:31 +0200)
> From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
> Date: Thu, 6 Jun 2024 07:46:31 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>, Philip Kaludercic <philipk@posteo.net>, 71356@debbugs.gnu.org
>
> Andrea is right. Reading through all the documentation, I implied
> that use-package would upgrade built-in packages if I pinned them to an archive
> and I :ensure'd them.
>
> Use case: want to upgrade org from the 9.6.x version packaged with master to the
> 9.7.x version available in elpa.
>
> Maybe this is more a FR and if so, we could move this to the list and have an informed
> discussion there.
I'd like to hear from Philip. If use-package just uses package.el,
then the behavior is expected.
Do you have package-install-upgrade-built-in set non-nil? If not, can
you set it non-nil and try the recipe again?
As for a feature request: what exactly is the feature requested here?
Are you saying that use-package should automatically upgrade built-in
packages? If so, I don't think this will fly, since it would mean
inconsistencies with package-install.
next prev parent reply other threads:[~2024-06-06 6:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 6:26 bug#71356: use-package doesn't load org from elpa Pedro Andres Aranda Gutierrez
2024-06-04 21:44 ` Andrea Corallo
2024-06-05 6:40 ` Pedro Andres Aranda Gutierrez
2024-06-05 11:18 ` Eli Zaretskii
2024-06-05 18:09 ` Andrea Corallo
2024-06-06 5:46 ` Pedro Andres Aranda Gutierrez
2024-06-06 6:02 ` Eli Zaretskii [this message]
2024-06-06 6:11 ` Pedro Andres Aranda Gutierrez
2024-06-06 9:15 ` Eli Zaretskii
2024-06-06 6:15 ` Philip Kaludercic
2024-06-06 9:21 ` Eli Zaretskii
2024-06-06 15:07 ` Pedro Andres Aranda Gutierrez
2024-06-06 15:19 ` Eli Zaretskii
2024-06-07 8:05 ` Pedro Andres Aranda Gutierrez
2024-06-10 6:02 ` Philip Kaludercic
2024-06-10 6:52 ` Pedro Andres Aranda Gutierrez
2024-06-10 8:17 ` Andrea Corallo
2024-06-10 12:18 ` Eli Zaretskii
2024-06-10 15:40 ` Philip Kaludercic
2024-06-10 16:12 ` Eli Zaretskii
2024-06-10 16:51 ` Pedro Andres Aranda Gutierrez
2024-06-10 17:46 ` Eli Zaretskii
2024-06-10 18:04 ` Philip Kaludercic
2024-06-11 5:27 ` Pedro Andres Aranda Gutierrez
2024-06-11 7:29 ` Eli Zaretskii
2024-06-11 7:53 ` Pedro Andres Aranda Gutierrez
2024-06-10 12:14 ` Eli Zaretskii
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=86ed9aip6z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71356@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=paaguti@gmail.com \
--cc=philipk@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).