unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sam Steingold <sds@gnu.org>
To: emacs-devel@gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: Org mode update breaking build?
Date: Tue, 09 May 2023 12:34:29 -0400	[thread overview]
Message-ID: <87lehx4g6i.fsf@gnu.org> (raw)
In-Reply-To: <83v8h9l5cw.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 03 May 2023 19:58:07 +0300")

> * Eli Zaretskii <ryvm@tah.bet> [2023-05-03 19:58:07 +0300]:
>
> We already fixed that, but only on master.  So you don't need to
> convince anyone that this needed fixing.  We are convinced.

I built from git master and did not get any errors.
However, when I visited an org-mode file, I got this:

--8<---------------cut here---------------start------------->8---
Debugger entered--Lisp error: (error "Org version mismatch.  Make sure that correct ‘load-path’ is set early in init.el")
  error("Org version mismatch.  Make sure that correct `load-path' is set early in init.el")
  byte-code(...)
  require(org-keys)
  byte-code(...)
  org-mode()
  set-auto-mode-0(org-mode nil)
  set-auto-mode()
  normal-mode(t)
  after-find-file(nil t)
  find-file-noselect-1(#<buffer xxx.txt> "~/xxx.txt" nil nil "~/xxx.txt" (1180547 66307))
  find-file-noselect("~/xxx.txt" nil nil t)
  find-file("~/xxx.txt" t)
  funcall-interactively(find-file "~/xxx.txt" t)
  command-execute(find-file)
--8<---------------cut here---------------end--------------->8---

(along with the usual long but worthless instructions)

While I agree that those who never use org can be happy with the change,
but I would argue that this is _worse_ for me (and other - willing or
unwilling - org users).

Basically, an apparently successful build no longer guarantees that the
resulting Emacs will be working.

It would seem that if the build process can detect this "Org version
mismatch", it should just `rm -f lisp/org/*.elc` and restart (remembering
that it tried this hack to avoid an infinite loop if it does not work).

Thank you!

-- 
Sam Steingold (https://aphar.dreamwidth.org/) on Pop 22.04 (jammy) X 11.0.12101004
https://lastingimpactpsychology.com https://steingoldpsychology.com
https://ffii.org https://www.memritv.org http://think-israel.org
Don't take life too seriously, you'll never get out of it alive!



  parent reply	other threads:[~2023-05-09 16:34 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 [this message]
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

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=87lehx4g6i.fsf@gnu.org \
    --to=sds@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).