From: Eli Zaretskii <eliz@gnu.org>
To: Tassilo Horn <tsdh@gnu.org>
Cc: tbading@web.de, emacs-devel@gnu.org
Subject: Re: Org mode update breaking build?
Date: Thu, 04 May 2023 08:13:24 +0300 [thread overview]
Message-ID: <83pm7gllvv.fsf@gnu.org> (raw)
In-Reply-To: <87ednxut4y.fsf@gnu.org> (message from Tassilo Horn on Wed, 03 May 2023 21:02:34 +0200)
> From: Tassilo Horn <tsdh@gnu.org>
> Cc: Tobias Bading <tbading@web.de>, emacs-devel@gnu.org
> Date: Wed, 03 May 2023 21:02:34 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > There's a solution on master, and an improvement on that solution in
> > the works,
>
> Is the solution commit 62e4eb8fcf7?
It's a major part of that, yes. Another important part is in commit
d80f959bed (in its part that changed org-macs.el).
> This commit is a week old but I would swear oath that I've had this
> org version mismatch error yesterday (or maybe two days ago?) on two
> different machines following the master branch. On both of them I
> update my emacs (almost) every morning.
You need to remove all the org/*.elc files, once, after that commit,
to adjust to the renaming of the variable that is an important part of
that fix.
> If my memory is correct and I get the error again, what information
> should I collect and attach to Bug#62762?
Run the failed compilation command manually and print the value of
org--inhibit-version-check while compiling the offending file.
prev parent reply other threads:[~2023-05-04 5:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 15:26 Org mode update breaking build? Tobias Bading
2023-05-03 15:55 ` Alan Mackenzie
2023-05-03 16:11 ` Tobias Bading
2023-05-03 16:58 ` Eli Zaretskii
2023-05-03 17:02 ` Tobias Bading
2023-05-04 4:42 ` Po Lu
2023-05-04 5:48 ` Eli Zaretskii
2023-05-09 16:34 ` Sam Steingold
2023-05-09 16:47 ` Eli Zaretskii
2023-05-09 17:17 ` Sam Steingold
2023-05-09 19:07 ` Eli Zaretskii
2023-05-10 18:12 ` Sam Steingold
2023-05-08 12:00 ` Madhu
2023-05-08 13:22 ` Eli Zaretskii
2023-05-14 5:49 ` Madhu
2023-05-14 5:59 ` Eli Zaretskii
2023-05-03 16:04 ` Eli Zaretskii
2023-05-03 16:07 ` Tobias Bading
2023-05-03 16:57 ` Eli Zaretskii
2023-05-03 18:56 ` John ff
2023-05-03 19:02 ` Tassilo Horn
2023-05-04 2:00 ` Michael Heerdegen
2023-05-04 3:23 ` Bob Rogers
2023-05-04 3:30 ` Michael Heerdegen
2023-05-04 3:44 ` Bob Rogers
2023-05-04 5:42 ` Eli Zaretskii
2023-05-04 5:58 ` Bob Rogers
2023-05-04 5:41 ` Eli Zaretskii
2023-05-04 5:13 ` Eli Zaretskii [this message]
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=83pm7gllvv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tbading@web.de \
--cc=tsdh@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 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.