From: Charles Philip Chan <firstname.lastname@example.org>
Subject: Re: Reinstalling compat fixed everything breaking
Date: Wed, 14 Sep 2022 13:19:56 -0400 [thread overview]
Message-ID: <87illpooub.fsf@MagnumOpus.khem> (raw)
In-Reply-To: <alpine.DEB.email@example.com> (William Denton's message of "Tue, 13 Sep 2022 20:26:28 -0400 (EDT)")
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
William Denton <firstname.lastname@example.org> writes:
> Yesterday I pulled the current source trees for Org and Emacs and compiled as
> I usually do ... and everything broke, with Org complaining about mixed
> versions, and all kinds of warnings and backtraces and "Invalid function:
> compat-declare-version" errors.
> After looking at various things I noticed a couple of mild warnings related to
> the package compat, which I'd seen for a while (several weeks, at least) but
> never bothered about, because everything worked. I thought maybe it was all
> connected, what with the new version-checking and such, and indeed "M-x
> package-reinstall compat" did the trick and now everything works.
I am seeing the same problem. However, it did not resolve for me after upgrading
the compat library to the current git version. I am still getting:
| Warning (emacs): Org version mismatch. Make sure that correct ‘load-path’ is
| set early in init.el This warning usually appears when a built-in Org version is
| loaded prior to the more recent Org version.
during "make install". I never had this problem before.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 219 bytes --]
next prev parent reply other threads:[~2022-09-14 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 0:26 Reinstalling compat fixed everything breaking William Denton
2022-09-14 17:19 ` Charles Philip Chan [this message]
2022-09-14 17:19 ` Charles Philip Chan
2022-09-14 18:02 ` William Denton
2022-09-15 14:24 ` Ihor Radchenko
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).