From: Tassilo Horn <tsdh@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: Yasushi SHOJI <yasushi.shoji@gmail.com>, emacs-devel@gnu.org
Subject: Re: emacs-29: let*: Symbol’s function definition is void: \(setf\ compat-alist-get\) with Magit
Date: Thu, 19 Jan 2023 10:57:48 +0100 [thread overview]
Message-ID: <875yd2c05o.fsf@gnu.org> (raw)
In-Reply-To: <87sfg6aowf.fsf@gmail.com>
Robert Pluim <rpluim@gmail.com> writes:
>>>>>> On Wed, 18 Jan 2023 19:39:54 +0100, Tassilo Horn <tsdh@gnu.org> said:
>
> Tassilo> The result of that coordination was that when API-breaking compat
> Tassilo> appeared, those packages had the required changes in place and
> Tassilo> required
> Tassilo> the new compat version. On package update, first the new compat
> Tassilo> was
> Tassilo> installed, then the packages using the compat library.
>
> Tassilo> However, it seems like when a package gets updated, it's not
> Tassilo> reloaded
> Tassilo> and thusly the packages using the compat library where compiled
> Tassilo> with the
> Tassilo> old compat version and that's why those errors popped up.
>
> Tassilo> Basically, there has been a compat (the package) change
> Tassilo> where after updating the compat package, one has to
> Tassilo> re-install magit (and other packages) using that new
> Tassilo> compat version. That is required because some macro has
> Tassilo> been changed.
>
> That could or could not be an Emacs bug. I guess weʼd need a recipe
> from 'emacs -Q' to be sure.
How would one create a recipe with emacs -Q when one is interested in
package updates? I guess one would rather use emacs -q in a testuser
account with no ~/.emacs.
I think what one has to do would create fake packages
macro-1.0
use-macro-1.0 requires macro-1.0
and install use-macro-1.0, macro-1.0 as a dependency. Then make a
breaking change in macro leading to macro-2.0 required by use-macro-2.0
which will error if use-macro-2.0 was compiled with macro-1.0 instead of
2.0.
Bye,
Tassilo
next prev parent reply other threads:[~2023-01-19 9:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 14:23 emacs-29: let*: Symbol’s function definition is void: \(setf\ compat-alist-get\) with Magit Yasushi SHOJI
2023-01-18 14:39 ` Robert Pluim
2023-01-18 15:48 ` Tassilo Horn
2023-01-18 16:59 ` Robert Pluim
2023-01-18 17:36 ` Eli Zaretskii
2023-01-18 18:25 ` [External] : " Drew Adams
2023-01-18 18:39 ` Tassilo Horn
2023-01-19 8:50 ` Robert Pluim
2023-01-19 9:57 ` Tassilo Horn [this message]
2023-01-25 17:17 ` Stefan Monnier
2023-01-18 18:54 ` Arash Esbati
2023-01-19 0:34 ` Yasushi SHOJI
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=875yd2c05o.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.com \
--cc=yasushi.shoji@gmail.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 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.