GNU bug report logs - #55198
[PATCH]: sbcl: Update to 2.2.4

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 55198 in the body.
You can then email your comments to 55198 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: André A. Gomes <andremegafone <at> gmail.com>
To: guix-patches <at> gnu.org
Subject: [PATCH]: sbcl: Update to 2.2.4
Date: Sat, 30 Apr 2022 18:36:24 +0100

[Message part 1 (text/plain, inline)]

Hi Guix,

Attached.  Thanks.


-- 
André A. Gomes
"You cannot even find the ruins..."

[0001-gnu-sbcl-Update-to-2.2.4.patch (text/x-patch, attachment)]

Message #8 received at 55198 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: André A. Gomes <andremegafone <at> gmail.com>
Cc: Guillaume Le Vaillant <glv <at> posteo.net>, 55198 <at> debbugs.gnu.org
Subject: Re: bug#55198: [PATCH]: sbcl: Update to 2.2.4
Date: Fri, 06 May 2022 10:24:58 +0200

Hi André,

André A. Gomes <andremegafone <at> gmail.com> skribis:

>>From 218a4273e317e4e1d2951c44f1f4b759db8cd3a5 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Andr=C3=A9=20A=2E=20Gomes?= <andremegafone <at> gmail.com>
> Date: Sat, 30 Apr 2022 18:33:02 +0100
> Subject: [PATCH] gnu: sbcl: Update to 2.2.4.
>
> * gnu/packages/lisp.scm (sbcl): Update to 2.2.4.

Guillaume, could you give it a go?

TIA.  :-)

Ludo’.

Message #11 received at 55198 <at> debbugs.gnu.org (full text, mbox):

From: Guillaume Le Vaillant <glv <at> posteo.net>
To: André A. Gomes <andremegafone <at> gmail.com>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 55198 <at> debbugs.gnu.org
Subject: Re: bug#55198: [PATCH]: sbcl: Update to 2.2.4
Date: Fri, 06 May 2022 08:38:26 +0000

[Message part 1 (text/plain, inline)]

Ludovic Courtès <ludo <at> gnu.org> skribis:

> Hi André,
>
> André A. Gomes <andremegafone <at> gmail.com> skribis:
>
>>>From 218a4273e317e4e1d2951c44f1f4b759db8cd3a5 Mon Sep 17 00:00:00 2001
>> From: =?UTF-8?q?Andr=C3=A9=20A=2E=20Gomes?= <andremegafone <at> gmail.com>
>> Date: Sat, 30 Apr 2022 18:33:02 +0100
>> Subject: [PATCH] gnu: sbcl: Update to 2.2.4.
>>
>> * gnu/packages/lisp.scm (sbcl): Update to 2.2.4.
>
> Guillaume, could you give it a go?
>
> TIA.  :-)
>
> Ludo’.

Hi,

When testing this updated sbcl I found out that it has a bug breaking
the sbcl-lzlib package (maybe others too). I reported it upstream and
they managed to fix it (https://bugs.launchpad.net/sbcl/+bug/1971088).

We could add a patch for the fix to sbcl 2.2.4, or just wait a few weeks
for the next release.

WDYT?

[signature.asc (application/pgp-signature, inline)]

Message #14 received at 55198 <at> debbugs.gnu.org (full text, mbox):

From: André A. Gomes <andremegafone <at> gmail.com>
To: Guillaume Le Vaillant <glv <at> posteo.net>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 55198 <at> debbugs.gnu.org
Subject: Re: bug#55198: [PATCH]: sbcl: Update to 2.2.4
Date: Fri, 06 May 2022 09:55:53 +0100

Guillaume Le Vaillant <glv <at> posteo.net> writes:

> When testing this updated sbcl I found out that it has a bug breaking
> the sbcl-lzlib package (maybe others too). I reported it upstream and
> they managed to fix it (https://bugs.launchpad.net/sbcl/+bug/1971088).
>
> We could add a patch for the fix to sbcl 2.2.4, or just wait a few weeks
> for the next release.

This is not exactly on topic but I'm wondering how should I proceed in
the future.  I checked that there was a new sbcl release, tried to build
locally and it succeeded.  What else should I do?  Thanks.

Perhaps we could wait until the next release.


-- 
André A. Gomes
"You cannot even find the ruins..."

Message #19 received at 55198-close <at> debbugs.gnu.org (full text, mbox):

From: Guillaume Le Vaillant <glv <at> posteo.net>
To: André A. Gomes <andremegafone <at> gmail.com>
Cc: Ludovic Courtès <ludo <at> gnu.org>,
 55198-close <at> debbugs.gnu.org
Subject: Re: bug#55198: [PATCH]: sbcl: Update to 2.2.4
Date: Fri, 06 May 2022 09:17:30 +0000

[Message part 1 (text/plain, inline)]

André A. Gomes <andremegafone <at> gmail.com> skribis:

> Guillaume Le Vaillant <glv <at> posteo.net> writes:
>
>> When testing this updated sbcl I found out that it has a bug breaking
>> the sbcl-lzlib package (maybe others too). I reported it upstream and
>> they managed to fix it (https://bugs.launchpad.net/sbcl/+bug/1971088).
>>
>> We could add a patch for the fix to sbcl 2.2.4, or just wait a few weeks
>> for the next release.
>
> This is not exactly on topic but I'm wondering how should I proceed in
> the future.  I checked that there was a new sbcl release, tried to build
> locally and it succeeded.  What else should I do?  Thanks.

After checking that the updated sbcl builds fine, you can also check all
the packages depending on sbcl with a command like:

--8<---------------cut here---------------start------------->8---
  ./pre-inst-env guix build $(./pre-inst-env guix refresh -l sbcl | cut -d ':' -f 2)
--8<---------------cut here---------------end--------------->8---


> Perhaps we could wait until the next release.

Ok. I'm closing this issue then, and you can open a new one to update to
sbcl 2.2.5 (or maybe 2.3.0?) when it it released (probably near the end
of May or beginning of June if upstream keeps the same release
schedule).

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.