From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.devel Subject: Re: emacs-29: let*: =?utf-8?Q?Symbol=E2=80=99s?= function definition is void: \(setf\ compat-alist-get\) with Magit Date: Thu, 19 Jan 2023 10:57:48 +0100 Message-ID: <875yd2c05o.fsf@gnu.org> References: <871qnrc3ey.fsf@gmail.com> <87zgafx2m9.fsf@gnu.org> <87wn5jaie6.fsf@gmail.com> <87fsc7y8wq.fsf@gnu.org> <87sfg6aowf.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14622"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.9.16; emacs 30.0.50 Cc: Yasushi SHOJI , emacs-devel@gnu.org To: Robert Pluim Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jan 19 11:22:28 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pIS3u-0003f0-OZ for ged-emacs-devel@m.gmane-mx.org; Thu, 19 Jan 2023 11:22:26 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pIRko-0001sr-Ek; Thu, 19 Jan 2023 05:02:42 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pIRki-0001mG-An for emacs-devel@gnu.org; Thu, 19 Jan 2023 05:02:36 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pIRki-0004jg-2K; Thu, 19 Jan 2023 05:02:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:In-reply-to:Date:Subject:To:From: References; bh=csqu673f5jTQ+T1YWu28Lp7JnJgi5jItJq8ciQANBBU=; b=mpTACIbY9fIaKk Vb/OwhlnNjmOVHlOS19gp831PVDRyB+FpJKobxRsKjz1OZDVWryCDeBTT2LKlNuk/pcC1fDRUkJd/ oAU4Fa7xTyiOxYoV4vetNUzwV9I/GBSYDP+Y0pyg6/xuLjvoxoPq5f/ub9jz7+LJxGxaENMq5B4gc ADPwQnHA7vhipKOQwD0+XfUqB864to5QRu+2+aCG+Kj7BzY96709d7cbzmIJXpt4bM0oN8hB7G2/X 56SrpQ5SRYauuO44EHRigBD14GB8k20uEEqrwiduWUyDu3jureJMRav9Qe+ES9ioG8fFGu4EE0jfO MEGlTCgV7GLYLVBq595w==; Original-Received: from auth1-smtp.messagingengine.com ([66.111.4.227]) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pIRkd-00039g-FG; Thu, 19 Jan 2023 05:02:34 -0500 Original-Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailauth.nyi.internal (Postfix) with ESMTP id DA02227C005A; Thu, 19 Jan 2023 05:02:30 -0500 (EST) Original-Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Thu, 19 Jan 2023 05:02:30 -0500 X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedruddutddgudduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfhgfhffvvefuffgjkfggtgfgsehtqhertddtreejnecuhfhrohhmpefvrghs shhilhhoucfjohhrnhcuoehtshguhhesghhnuhdrohhrgheqnecuggftrfgrthhtvghrnh epgfettdduiedvhfffhfefhfevhfeuvdehjeejfeelffehkeffuedthffgjeeihfegnecu vehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhrnh domhgvshhmthhprghuthhhphgvrhhsohhnrghlihhthidqkeeijeefkeejkeegqdeifeeh vdelkedqthhsughhpeepghhnuhdrohhrghesfhgrshhtmhgrihhlrdhfmh X-ME-Proxy: Feedback-ID: ib2b94485:Fastmail Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 19 Jan 2023 05:02:30 -0500 (EST) In-reply-to: <87sfg6aowf.fsf@gmail.com> X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:302538 Archived-At: Robert Pluim writes: >>>>>> On Wed, 18 Jan 2023 19:39:54 +0100, Tassilo Horn said: > > Tassilo> The result of that coordination was that when API-breaking c= ompat > Tassilo> appeared, those packages had the required changes in place a= nd > Tassilo> required > Tassilo> the new compat version. On package update, first the new co= mpat > 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 compi= led > 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=CA=BCd 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