From: Max Nikulin <manikulin@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-orgmode@gnu.org, 59882@debbugs.gnu.org
Subject: bug#59882: Multiple versions of Org in load-path problem
Date: Thu, 6 Apr 2023 23:09:13 +0700 [thread overview]
Message-ID: <7e64ae5e-6fd7-ea41-dae5-c8abd9a3fefa__3157.20662926964$1680797426$gmane$org@gmail.com> (raw)
In-Reply-To: <jwvh6xsybez.fsf-monnier+emacs@gnu.org>
On 18/12/2022 22:40, Stefan Monnier via Bug reports for GNU Emacs, the
Swiss army knife of text editors wrote:
>> - "emacs -l org" to simulate a regular user session with some opened files.
>> - Update to Org-9.6 from ELPA.
>> - Close emacs and start it again "emacs -l org"
>>
>> Result:
>> byte-code: Invalid function: org-assert-version
>
> Hmm... there's code in `package.el` intended to avoid that problem, but
> clearly it's failing here. Could Someone™ investigate why that code
> doesn't do its job.
>
> The code in question is in `package--reload-previously-loaded`
Since I managed to reproduce the issue with emacs-28.2 built from source
tree, I tried current master (30.0.50) as well. I used the following
trick to shadow org-assert-version:
sed -i -e 's/org-assert-version/org-assert-version-old/g' lisp/org/*.el
I am unable to reproduce the "Invalid function: org-assert-version"
issue. Org compilation finishes without warnings.
I have noticed that neither `package--reload-previously-loaded` nor code
loading already compiled package unload the loaddefs file. E.g. I added
org-stale-function marked as autoload. It is possible to get help for
this function, but attempts to call this function causes "Autoloading
file" error. Ideally emacs should completely forget about such functions
when newer elpa package is installed.
next prev parent reply other threads:[~2023-04-06 16:09 UTC|newest]
Thread overview: 105+ 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
2022-12-08 21:56 ` bug#59882: " David Masterson
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:17 ` Eli Zaretskii
2022-12-09 7:43 ` David Masterson
2022-12-09 11:57 ` Eli Zaretskii
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-09 20:27 ` Eli Zaretskii
2022-12-09 19:51 ` David Masterson
2022-12-09 19:40 ` Cook, Malcolm
2022-12-09 7:43 ` David Masterson
2022-12-10 14:01 ` Ihor Radchenko
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 13:37 ` Ihor Radchenko
2022-12-14 14:35 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-14 14:35 ` Stefan Monnier
2022-12-14 16:02 ` Max Nikulin
2022-12-14 16:02 ` Max Nikulin
2022-12-15 4:17 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-15 4:17 ` Stefan Monnier
2022-12-15 4:56 ` Ihor Radchenko
2022-12-15 4:56 ` Ihor Radchenko
2022-12-16 12:36 ` Max Nikulin
2022-12-16 14:47 ` Ihor Radchenko
2022-12-16 14:47 ` Ihor Radchenko
2022-12-18 15:24 ` Max Nikulin
2022-12-18 15:24 ` Max Nikulin
2022-12-18 15:40 ` Stefan Monnier
2022-12-18 15:40 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-06 16:09 ` Max Nikulin
2023-04-06 21:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-06 21:25 ` Stefan Monnier
2023-04-19 4:20 ` Tom Gillespie
2023-04-19 4:20 ` Tom Gillespie
2023-04-06 16:09 ` Max Nikulin [this message]
2022-12-25 9:48 ` Ihor Radchenko
2022-12-25 11:46 ` Max Nikulin
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-26 12:25 ` Max Nikulin
2022-12-27 9:47 ` Ihor Radchenko
2022-12-27 9:47 ` Ihor Radchenko
2022-12-27 9:56 ` Max Nikulin
2022-12-27 9:56 ` Max Nikulin
2023-02-03 11:02 ` Ihor Radchenko
2023-02-03 11:02 ` Ihor Radchenko
2023-02-03 12:15 ` Eli Zaretskii
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-16 12:14 ` Max Nikulin
2023-02-21 5:22 ` Richard Stallman
2023-02-21 5:22 ` Richard Stallman
2023-02-21 12:32 ` Eli Zaretskii
2023-02-21 12:32 ` Eli Zaretskii
2023-02-21 17:26 ` Bhavin Gandhi
2023-02-21 17:26 ` Bhavin Gandhi
2023-02-22 10:48 ` Ihor Radchenko
2023-02-22 16:58 ` Bhavin Gandhi
2023-02-22 16:58 ` Bhavin Gandhi
2023-02-23 9:35 ` Ihor Radchenko
2023-02-23 9:35 ` Ihor Radchenko
2023-02-22 10:48 ` Ihor Radchenko
2023-02-14 22:53 ` Gregor Zattler
2023-04-06 15:02 ` Max Nikulin
2023-04-06 15:02 ` Max Nikulin
2023-04-07 11:39 ` Max Nikulin
2022-12-26 11:01 ` Ihor Radchenko
2022-12-26 8:44 ` Ihor Radchenko
2022-12-25 9:48 ` Ihor Radchenko
2022-12-16 12:36 ` Max Nikulin
2022-12-14 14:25 ` Stefan Monnier
2022-12-14 14:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-14 12:59 ` Eli Zaretskii
2022-12-14 21:49 ` Cook, Malcolm
2022-12-14 21:49 ` Cook, Malcolm
2022-12-14 9:51 ` Ihor Radchenko
2022-12-09 19:47 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='7e64ae5e-6fd7-ea41-dae5-c8abd9a3fefa__3157.20662926964$1680797426$gmane$org@gmail.com' \
--to=manikulin@gmail.com \
--cc=59882@debbugs.gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.