[bug#71857] [PATCH] gnu: sbcl: Update to 2.4.6.

[bug#71857] [PATCH] gnu: sbcl: Update to 2.4.6.

[ashish.is--- via Guix-patches via]

From: Ashish SHUKLA <ashish.is@lostca.se>

* gnu/packages/lisp.scm (sbcl): Update to 2.4.6.

Change-Id: Ia9e6138202f4dae28ddf9bd373da49d3cc0d21c6
---
 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 1b985362b1..6c676f7feb 100644
--- a/gnu/packages/lisp.scm
+++ b/gnu/packages/lisp.scm
@@ -1272,14 +1272,14 @@ (define-public s7
 (define-public sbcl
   (package
     (name "sbcl")
-    (version "2.4.5")
+    (version "2.4.6")
     (source
      (origin
        (method url-fetch)
        (uri (string-append "mirror://sourceforge/sbcl/sbcl/" version "/sbcl-"
                            version "-source.tar.bz2"))
        (sha256
-        (base32 "1lbvb9rzlkl3h8s75i2js4dnmgxmvs41jxjb5dj0f603r688xxjd"))
+        (base32 "149h7xyadg13f3xs3v7klap0lrsngazqaafn4qbrmq6s89w912d4"))
        (modules '((guix build utils)))
        (snippet
         '(begin

base-commit: c7b009285ec2ab7a27747de40f28e6ecfba82922
-- 
2.45.2

[bug#71857] [PATCH] gnu: sbcl: Update to 2.4.6.

[jgart via Guix-patches via]

Nice! Thanks for the contribution.

I'll let Guillaume review this since I have limited CPU resources on my machine to build everything that depends on sbcl and QA is currently in an unknown state.

Hi Christopher,

Do you have any suggestions for what to do when QA is in an unknown state?

all the best,

jgart

[bug#71857] [PATCH] gnu: sbcl: Update to 2.4.6.

[Christopher Baines]

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

"jgart" <jgart@dismail.de> writes:

> Nice! Thanks for the contribution.
>
> I'll let Guillaume review this since I have limited CPU resources on my machine to build everything that depends on sbcl and QA is currently in an unknown state.
>
> Hi Christopher,
>
> Do you have any suggestions for what to do when QA is in an unknown state?

In this case, QA might eventually get around to processing this change,
but it's probably not going to build things since there are quite a few
dependent packages.

What you can do though is retitle the issue to indicate that this'll
need to go to a topic branch (e.g. lisp-team). To do that you'd send
something like the following to control@debbugs.gnu.org:

retitle 71857 [lisp-team] gnu: sbcl: Update to 2.4.6.
thanks

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

[bug#71857] [PATCH lisp-team v2] gnu: sbcl: Update to 2.4.7.

[Ashish SHUKLA via Guix-patches via]

* gnu/packages/lisp.scm (sbcl): Update to 2.4.7.

Change-Id: Ie8528c75d0bc939cde8faebd80e7a3e0ada82914
---
 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 97f7dd357b..a050e44e98 100644
--- a/gnu/packages/lisp.scm
+++ b/gnu/packages/lisp.scm
@@ -1272,14 +1272,14 @@ (define-public s7
 (define-public sbcl
   (package
     (name "sbcl")
-    (version "2.4.5")
+    (version "2.4.7")
     (source
      (origin
        (method url-fetch)
        (uri (string-append "mirror://sourceforge/sbcl/sbcl/" version "/sbcl-"
                            version "-source.tar.bz2"))
        (sha256
-        (base32 "1lbvb9rzlkl3h8s75i2js4dnmgxmvs41jxjb5dj0f603r688xxjd"))
+        (base32 "1lhia29g0byj7w3akd99sjb8kxp95adwqk2kbl0wsnk30cjlsm38"))
        (modules '((guix build utils)))
        (snippet
         '(begin

base-commit: fdc6274de5b1d617fcabb3f3af9d2c0dd2a6520d
-- 
2.45.2

bug#71857: [PATCH lisp-team v2] gnu: sbcl: Update to 2.4.7.

[Guillaume Le Vaillant]

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

Patch applied as 08ec4e8e7282837ee0ba1b85c6d91d579a8cc08f.
Thanks.

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