From: Tim Cross <theophilusx@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Unable to get current or via use-package
Date: Fri, 11 Feb 2022 05:39:11 +1100 [thread overview]
Message-ID: <87bkzey2f6.fsf@gmail.com> (raw)
In-Reply-To: <87ee4bumc4.fsf@localhost>
Ihor Radchenko <yantar92@gmail.com> writes:
> Tim Cross <theophilusx@gmail.com> writes:
>
>>> Is that necessary? Can't I just use the package manager to update Org
>>> along with any other packages? Or does the issue about not visiting and
>>> .org file before installing via the package manager apply to updates
>>> too?
>>>
>>
>> Even with updates, it is still important that no existing org
>> functionality has been loaded to avoid potential inconsistencies due to
>> mixed version installation. For updates within the same version (i.e.
>> bug fix updates), the risk is low, but may still result in an
>> inconsistent build.
>
> It looks like there was an attempt to fix mixed compilation issue in
> package.el See
> https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=c13baa10d55ec863d3ceaea48c6b2959ece98198
> and https://debbugs.gnu.org/cgi/bugreport.cgi?bug=10125
>
> If I understand that thread correctly, package.el should not have issues
> with mixed compilation. Not so sure about straight.el and certainly it
> will not solve the problem when part of built-in Org is loaded before
> the newer Org version is added to the load-path.
>
Thanks for the info. However, I'm not confident that has addressed the
full issue. I note that patch is from 2014. There has certainly been a
number of people report mixed installation problems since that patch
would have been applied and part of their current version of package.el.
As you point out, we don't know what happens with other package managers
like straight.el and you are likely to get this issue if part of the
built-in version has been loaded before package.el attempts to load the
new version, so that might explain these later reports.
Would seem the best approach and simplest solution is still to ensure no
org functionality has been loaded before attempting an update.
next prev parent reply other threads:[~2022-02-10 19:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 13:25 Unable to get current or via use-package Loris Bennett
2022-02-09 14:02 ` Eric S Fraga
2022-02-09 15:51 ` Loris Bennett
2022-02-09 17:18 ` Greg Minshall
2022-02-10 20:57 ` João Pedro de Amorim Paula
2022-02-10 21:01 ` João Pedro de Amorim Paula
2022-02-17 15:00 ` Loris Bennett
2022-02-18 21:32 ` João Pedro de Amorim Paula
2022-02-18 21:36 ` João Pedro de Amorim Paula
2022-02-21 6:40 ` Loris Bennett
2022-02-09 16:28 ` Cook, Malcolm
2022-02-10 7:09 ` Loris Bennett
2022-02-10 8:12 ` Tim Cross
2022-02-10 9:01 ` Ihor Radchenko
2022-02-10 18:39 ` Tim Cross [this message]
2022-02-10 15:19 ` Cook, Malcolm
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkzey2f6.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).