From: "ashish.is--- via Guix-patches" via <guix-patches@gnu.org>
To: 72623@debbugs.gnu.org
Cc: Ashish SHUKLA <ashish.is@lostca.se>,
Guillaume Le Vaillant <glv@posteo.net>,
Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>,
Munyoki Kilyungi <me@bonfacemunyoki.com>,
Sharlatan Hellseher <sharlatanus@gmail.com>,
jgart <jgart@dismail.de>
Subject: [bug#72623] [PATCH] gnu: ccl: Update to 1.13
Date: Wed, 14 Aug 2024 17:44:34 +0200 [thread overview]
Message-ID: <ead4ac5184b5d66e92f774c1871ff2c531f40fe6.1723650274.git.ashish.is@lostca.se> (raw)
From: Ashish SHUKLA <ashish.is@lostca.se>
* gnu/packages/lisp.scm (ccl): Update to 1.13.
[inputs] Update ccl bootstrap souirces.
Change-Id: Id2b9d29b4ea51aba23ca1aee770e33755b062b19
---
gnu/packages/lisp.scm | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/gnu/packages/lisp.scm b/gnu/packages/lisp.scm
index 97f7dd357b..d78ca5ddb5 100644
--- a/gnu/packages/lisp.scm
+++ b/gnu/packages/lisp.scm
@@ -230,7 +230,7 @@ (define-public ccl
(name "ccl")
;; XXX When updating this package, check whether we can simply append
;; VERSION to the ccl-bootstrap URL again, instead of per architecture.
- (version "1.12.1")
+ (version "1.13")
(source (origin
(method git-fetch)
(uri (git-reference
@@ -239,7 +239,7 @@ (define-public ccl
(file-name (git-file-name "ccl" version))
(sha256
(base32
- "1zz291lvsrr7pps8wfl2kdxsnzjngqi4v3mil14pga4r5zanmsi7"))))
+ "12cb3gp43bhl7nyms3a4lix8j1s3arnp124d3ahc2lhlrjirs0mr"))))
(build-system gnu-build-system)
;; CCL consists of a "lisp kernel" and "heap image", both of which are
;; shipped in precompiled form in source tarballs. The former is a C
@@ -253,18 +253,18 @@ (define-public ccl
(uri (string-append
"https://github.com/Clozure/ccl/releases/download/v"
(match (%current-system)
- ("armhf-linux" "1.12/linuxarm")
+ ("armhf-linux" "1.13/linuxarm")
;; XXX: This source only works on x86, but provide it as a
;; catch-all to prevent errors when querying this package
;; on unsupported platforms.
- (_ "1.12.1/linuxx86"))
+ (_ "1.13/linuxx86"))
".tar.gz"))
(sha256
(base32
(match (%current-system)
("armhf-linux"
- "0x4bjx6cxsjvxyagijhlvmc7jkyxifdvz5q5zvz37028va65243c")
- (_ "0ll017ajcfsyx8f7zsy4394y8xxvz40iz0gcsmznp0n3mf0xi67c"))))))))
+ "0isihnk275yqz6wn34ab38g7lf1nq0sqc00h0g22fvw77d60q9cb")
+ (_ "04ry8zwrcjjmzbxp43nkknchabk6i6mclrzg5biwfp1h64bcnzfx"))))))))
(native-inputs
(list cl-asdf m4))
(arguments
base-commit: aadc73c8d1a622f76ee02aca22eb89c83023680f
--
2.46.0
next reply other threads:[~2024-08-14 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 15:44 ashish.is--- via Guix-patches via [this message]
2024-08-15 12:26 ` bug#72623: [PATCH] gnu: ccl: Update to 1.13 Guillaume Le Vaillant
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ead4ac5184b5d66e92f774c1871ff2c531f40fe6.1723650274.git.ashish.is@lostca.se \
--to=guix-patches@gnu.org \
--cc=72623@debbugs.gnu.org \
--cc=ashish.is@lostca.se \
--cc=cox.katherine.e+guix@gmail.com \
--cc=glv@posteo.net \
--cc=jgart@dismail.de \
--cc=me@bonfacemunyoki.com \
--cc=sharlatanus@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).