From: "Michel Schinz" <michel@schi.nz>
To: "Berry,
Charles via General discussions about Org-mode."
<emacs-orgmode@gnu.org>
Subject: Re: Multiple versions of Org in load-path problem
Date: Thu, 08 Dec 2022 20:31:13 +0100 [thread overview]
Message-ID: <39a5810d-75bc-4ddb-8722-703f762ed4de@app.fastmail.com> (raw)
In-Reply-To: <SJ0PR03MB54550C7727696BE317D0DD13A21D9@SJ0PR03MB5455.namprd03.prod.outlook.com>
Just for the record, I also ran into problems when installing Org 9.6
using Emacs' package system on top of an older version that came with
Emacs. If I tried to install it as usual (M-x list-packages, then
install the package from there), I had errors during compilation related
to `org-assert-version`, and then if I restarted Emacs, I would get a
fatal error in an unrelated package.
I managed to solve that problem by:
1. uninstalling Org 9.6 and exiting Emacs,
2. starting Emacs with -q,
3. installing Org 9.6 from there (using M-x list-packages as usual),
4. restarting Emacs.
I'm not sure this is related to your problem, or whether that helps (but
I hope it does)...
Michel.
On Thu, 8 Dec 2022, at 19:24, David Masterson wrote:
> Ihor Radchenko <yantar92@posteo.net> writes:
>
>> David Masterson <dsmasterson@gmail.com> writes:
>>
>>> I went so far as to add the following to early-init.el:
>>>
>>> (if (featurep 'org) (unload-feature 'org))
>>> (add-to-list 'load-path (expand-file-name "~/.emacs.d/elpa/org-9.6")
>>> (load-library "org")
>>>
>>> The load-library still fails with the org-assert-version error.
>>
>> Indeed. It is to be expected. M-x package-install should not err here
>> though. In theory.
>
> My testing says that, in early-init.el, Org is not yet a feature, so the
> built-in Org-9.3 is not yet loaded and the first 'if' fails. Adding the
> path for Org-9.6 should put it at the front of the load-path and
> (hopefully) override Org-9.3 if it is in the load-path (I think I
> checked that). The error in the load-library is, therefore, a problem
> with Org-9.6 installed by package-install.
>
>> I suggest you to read `org-assert-version'. It aims to catch the
>> situation above and similar.
>
> This is chicken and egg problem. I can't use 'org-assert-version'
> unless I can get Org to load.
>
>> Note, however, that installation problem is different. Or rather it
>> should be different.
>>
>>> Could it be that, when you package-install Org-9.6, it runs through a
>>> check where (I think) it compiles the package? I get a lot of warnings
>>> and 34(?) failed files. Could it be that some of the files are not
>>> built and, so, when I load-library, I'm picking up some of the wrong
>>> files from the built-in Org-9.3? Do we need to remove all versions of
>>> Org that is not the current version from the load-path at the very
>>> beginning of org.el to ensure no fall-through? Kind of a hack, but...
>>
>> Maybe. It should not. That's why I raised
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=59882
>> I'd like to see if Emacs devs have anything to say here.
>
> Good. I'm not used to bug reporting in Emacs, so I raised a question on
> use-package in emacs-devel@gnu.org, but they pointed me at your bug.
> I'll see if I can add anything there.
>
> --
> David Masterson
next prev parent reply other threads:[~2022-12-08 19:32 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 2:50 Multiple versions of Org in load-path problem David Masterson
2022-12-06 5:36 ` tomas
2022-12-06 7:04 ` David Masterson
2022-12-07 13:30 ` Ihor Radchenko
2022-12-08 3:27 ` David Masterson
2022-12-08 7:16 ` David Masterson
2022-12-08 7:26 ` Ihor Radchenko
2022-12-08 18:24 ` David Masterson
2022-12-08 19:31 ` Michel Schinz [this message]
2022-12-08 21:56 ` David Masterson
2022-12-08 22:56 ` Tim Cross
2022-12-09 5:00 ` David Masterson
2022-12-09 6:56 ` Tim Cross
2022-12-09 15:49 ` Sharon Kimble
2022-12-10 20:38 ` Tom Gillespie
2022-12-09 7:17 ` bug#59882: " Eli Zaretskii
2022-12-09 7:43 ` David Masterson
2022-12-09 11:57 ` Eli Zaretskii
2022-12-09 19:40 ` Cook, Malcolm
2022-12-09 19:51 ` David Masterson
2022-12-09 20:27 ` Eli Zaretskii
2022-12-10 14:01 ` Ihor Radchenko
2022-12-14 9:51 ` Ihor Radchenko
2022-12-14 12:59 ` Eli Zaretskii
2022-12-14 13:37 ` Ihor Radchenko
2022-12-14 14:35 ` Stefan Monnier
2022-12-14 16:02 ` Max Nikulin
2022-12-15 4:17 ` Stefan Monnier
2022-12-15 4:56 ` Ihor Radchenko
2022-12-16 12:36 ` Max Nikulin
2022-12-16 14:47 ` Ihor Radchenko
2022-12-18 15:24 ` Max Nikulin
2022-12-18 15:40 ` Stefan Monnier
2023-04-06 16:09 ` Max Nikulin
2023-04-06 21:25 ` Stefan Monnier
2023-04-19 4:20 ` Tom Gillespie
2022-12-25 9:48 ` Ihor Radchenko
2022-12-25 11:46 ` Max Nikulin
2022-12-26 8:44 ` Ihor Radchenko
2022-12-26 11:01 ` Ihor Radchenko
2022-12-26 12:25 ` Max Nikulin
2022-12-27 9:47 ` Ihor Radchenko
2022-12-27 9:56 ` Max Nikulin
2023-02-03 11:02 ` Ihor Radchenko
2023-02-03 12:15 ` Eli Zaretskii
2023-02-03 20:01 ` Tim Cross
2023-02-14 22:53 ` Gregor Zattler
2023-02-16 12:14 ` Max Nikulin
2023-02-21 5:22 ` Richard Stallman
2023-02-21 12:32 ` Eli Zaretskii
2023-02-21 17:26 ` Bhavin Gandhi
2023-02-22 10:48 ` Ihor Radchenko
2023-02-22 16:58 ` Bhavin Gandhi
2023-02-23 9:35 ` Ihor Radchenko
2023-04-06 15:02 ` Max Nikulin
2022-12-14 14:25 ` Stefan Monnier
2022-12-14 21:49 ` Cook, Malcolm
2022-12-09 19:47 ` Cook, Malcolm
2022-12-08 21:50 ` Cook, Malcolm
[not found] ` <87o7se74bf.fsf@penguin>
2022-12-08 7:19 ` David Masterson
2022-12-08 9:10 ` 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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39a5810d-75bc-4ddb-8722-703f762ed4de@app.fastmail.com \
--to=michel@schi.nz \
--cc=emacs-orgmode@gnu.org \
/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).