From: Artyom Bologov <mail@aartaka.me>
To: 66074@debbugs.gnu.org
Subject: [bug#66074] [PATCH] gnu: sbcl-njson: Update to 1.2.1.
Date: Mon, 18 Sep 2023 19:38:55 +0400 [thread overview]
Message-ID: <87edivo5h6.fsf@aartaka.me> (raw)
[-- Attachment #1: Type: text/plain, Size: 84 bytes --]
Hello Guix,
Find the patch updating sbcl-njson to 1.2.1 attached to this message.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Update sbcl-njson to 1.2.1. --]
[-- Type: text/x-patch, Size: 1222 bytes --]
From 1242fc1de53581fb5b6ae2b149288fc8686deedd Mon Sep 17 00:00:00 2001
From: Artyom Bologov <mail@aartaka.me>
Date: Mon, 18 Sep 2023 19:37:39 +0400
Subject: [PATCH] gnu: sbcl-njson: Update to 1.2.1.
* gnu/packages/lisp-xyz.scm (sbcl-njson): Update to 1.2.1.
---
gnu/packages/lisp-xyz.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/lisp-xyz.scm b/gnu/packages/lisp-xyz.scm
index c6f66db840..752b777ed2 100644
--- a/gnu/packages/lisp-xyz.scm
+++ b/gnu/packages/lisp-xyz.scm
@@ -26603,7 +26603,7 @@ (define-public ecl-nkeymaps
(define-public sbcl-njson
(package
(name "sbcl-njson")
- (version "1.2.0")
+ (version "1.2.1")
(source (origin
(method git-fetch)
(uri (git-reference
@@ -26612,7 +26612,7 @@ (define-public sbcl-njson
(file-name (git-file-name "cl-njson" version))
(sha256
(base32
- "1zsf7sm88wjrd4da5bvpxi8fvsx01cv51p8820fnj062x6hlhg38"))))
+ "0p3zvn3jfzcdzpvikdaw3g14wfsklq0msw0rjaxin3aa7vmqpyqk"))))
(build-system asdf-build-system/sbcl)
(inputs (list sbcl-cl-json sbcl-jzon))
(native-inputs (list sbcl-lisp-unit2))
--
2.41.0
[-- Attachment #3: Type: text/plain, Size: 28 bytes --]
Thanks,
--
Artyom Bologov.
next reply other threads:[~2023-09-18 15:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 15:38 Artyom Bologov [this message]
2023-09-21 15:38 ` bug#66074: [PATCH] gnu: sbcl-njson: Update to 1.2.1 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edivo5h6.fsf@aartaka.me \
--to=mail@aartaka.me \
--cc=66074@debbugs.gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.