[bug#55198] [PATCH]: sbcl: Update to 2.2.4

[bug#55198] [PATCH]: sbcl: Update to 2.2.4

[André A. Gomes]

[-- Attachment #1: Type: text/plain, Size: 95 bytes --]

Hi Guix,

Attached.  Thanks.


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-gnu-sbcl-Update-to-2.2.4.patch --]
[-- Type: text/x-patch, Size: 1108 bytes --]

From 218a4273e317e4e1d2951c44f1f4b759db8cd3a5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20A=2E=20Gomes?= <andremegafone@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.
---
 gnu/packages/lisp.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/lisp.scm b/gnu/packages/lisp.scm
index d5f1e94269..1f17167518 100644
--- a/gnu/packages/lisp.scm
+++ b/gnu/packages/lisp.scm
@@ -413,14 +413,14 @@ (define-public clisp
 (define-public sbcl
   (package
     (name "sbcl")
-    (version "2.2.2")
+    (version "2.2.4")
     (source
      (origin
        (method url-fetch)
        (uri (string-append "mirror://sourceforge/sbcl/sbcl/" version "/sbcl-"
                            version "-source.tar.bz2"))
        (sha256
-        (base32 "1xjhg473ibfiplvvyg1grxrh0nqqbg72acc2pcacw7bijyzdp447"))))
+        (base32 "00kjlnvq80b0k5s7z8b9m9kf26wdhi375mqaxl4gixv5phf2bpgw"))))
     (build-system gnu-build-system)
     (outputs '("out" "doc"))
     (native-inputs
-- 
2.35.1

[bug#55198] [PATCH]: sbcl: Update to 2.2.4

[Ludovic Courtès]

Hi André,

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

>>From 218a4273e317e4e1d2951c44f1f4b759db8cd3a5 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Andr=C3=A9=20A=2E=20Gomes?= <andremegafone@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’.

[bug#55198] [PATCH]: sbcl: Update to 2.2.4

[Guillaume Le Vaillant]

[-- Attachment #1: Type: text/plain, Size: 818 bytes --]

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

> Hi André,
>
> André A. Gomes <andremegafone@gmail.com> skribis:
>
>>>From 218a4273e317e4e1d2951c44f1f4b759db8cd3a5 Mon Sep 17 00:00:00 2001
>> From: =?UTF-8?q?Andr=C3=A9=20A=2E=20Gomes?= <andremegafone@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?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

[bug#55198] [PATCH]: sbcl: Update to 2.2.4

[André A. Gomes]

Guillaume Le Vaillant <glv@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..."

bug#55198: [PATCH]: sbcl: Update to 2.2.4

[Guillaume Le Vaillant]

[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]

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

> Guillaume Le Vaillant <glv@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).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]