unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "T.V Raman" <raman@google.com>, emacs-devel@gnu.org
Subject: Re: Org breakage after rebuilding from Git
Date: Fri, 19 May 2023 09:20:11 +0200	[thread overview]
Message-ID: <87sfbs91iu.fsf@gnu.org> (raw)
In-Reply-To: <83lehlvfdo.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> Debugger entered--Lisp error: (error "Org version mismatch.  Make
>> sure that correct ‘loa...")  (signal error ("Org version mismatch.
>> Make sure that correct ‘loa..."))  (error "Org version mismatch.
>> Make sure that correct `loa...")
>
> Remove all the *.elc files in lisp/org, then rebuild Emacs, and the
> problem should go away.

I've had this issue when building emacs, too, and you informed me that
there's a fix in master for that.  And indeed, emacs now builds fine.
However, my personal update script goes

  1. cd ~/Repos/el/emacs/ && git pull && make
  2. ~/Repos/el/emacs/src/emacs -batch -l ~/.emacs.d/init.el -f package-upgrade-all

so now instead of failing in step 1 on org changes, I fail in step 2
(probably because my init.el somehow loads org) which is not better.  Is
the fix really about deferring the error from compile time to runtime?
That would help users who never ever load org, I guess, but even for
sporadic users of small parts of it like me, it's actually worse.

I guess I could add some check to my update script like

  src/emacs --batch --eval "(require 'org)" || begin rm lisp/org/*.elc && make; end

between step 1 and 2...

Bye,
Tassilo



  reply	other threads:[~2023-05-19  7:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 14:40 Org breakage after rebuilding from Git T.V Raman
2023-05-18 15:16 ` Eli Zaretskii
2023-05-19  7:20   ` Tassilo Horn [this message]
2023-05-19 10:58     ` 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=87sfbs91iu.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=raman@google.com \
    /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).