From: Ihor Radchenko <yantar92@posteo.net>
To: 59882@debbugs.gnu.org
Subject: bug#59882: 30.0.50; Compilation of ELPA packages during version upgrade (Org 9.6 ELPA upgrade from older ELPA version)
Date: Wed, 07 Dec 2022 11:36:07 +0000 [thread overview]
Message-ID: <87mt7zh2e0.fsf@localhost> (raw)
Hi,
I am writing as a follow-up of numerous errors reports on Org 9.6
upgrades.
Users commonly report issues upgrading Org mode via ELPA when an older,
non-built-in, version of Org is already installed and loaded.
The issue is well described in https://irreal.org/blog/?p=10996
People are commonly getting "invalid function `org-assert-version'",
which indicates compilation issue when `org-assert-version' macro is not
correctly recognized as a macro.
Similar errors have been reported in the past Org upgrades when we
introduced/changes some basic macros in Org.
I am not yet sure about the source of the error, but I suspect that it
might be something to do with package.el. May it be that M-x
package-install / package-reinstall does not unload the old package
versions upon installation? Or maybe there are some stale .elc files
lying around? Any other ideas?
P.S. Please, do not be diverted by the purpose of `org-assert-version'
macro. The origin of the error has nothing to do with it and could as
well happen with any other macro. It is just that we put this particular
macro into all the Org libraries now, making the problem obvious.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
reply other threads:[~2022-12-07 11:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87mt7zh2e0.fsf@localhost \
--to=yantar92@posteo.net \
--cc=59882@debbugs.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.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).