From: "André A. Gomes" <andremegafone@gmail.com>
To: 64853@debbugs.gnu.org
Cc: pierre@atlas.engineer
Subject: [bug#64853] [PATCH]: Update sbcl-nasdf to 0.1.6
Date: Tue, 25 Jul 2023 14:36:34 +0300 [thread overview]
Message-ID: <874jlsz0hp.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 117 bytes --]
Hi Guix,
Please find the patch 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-nasdf-Update-to-0.1.6.patch --]
[-- Type: text/x-patch, Size: 1312 bytes --]
From 0f049a321fd85b30260e9c41c69d8904a4739adc Mon Sep 17 00:00:00 2001
From: "Andre A. Gomes" <andremegafone@gmail.com>
Date: Tue, 25 Jul 2023 14:34:55 +0300
Subject: [PATCH] gnu: sbcl-nasdf: Update to 0.1.6.
* gnu/packages/lisp-xyz.scm (sbcl-nasdf): Update to 0.1.6.
---
gnu/packages/lisp-xyz.scm | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gnu/packages/lisp-xyz.scm b/gnu/packages/lisp-xyz.scm
index 9ef315ff94..05a9e8878c 100644
--- a/gnu/packages/lisp-xyz.scm
+++ b/gnu/packages/lisp-xyz.scm
@@ -25673,10 +25673,10 @@ (define-public cl-nfiles
(package-inputs sbcl-nfiles)))))
(define-public sbcl-nasdf
- (let ((commit "5d823d97282e11cecd8da9bcb255c4a8ead1ba93"))
+ (let ((commit "73c89680ace25929c2a1ccc0809db99e9edffa07"))
(package
(name "sbcl-nasdf")
- (version "0.1.5")
+ (version "0.1.6")
(source
(origin
(method git-fetch)
@@ -25686,7 +25686,7 @@ (define-public sbcl-nasdf
(file-name (git-file-name "cl-ntemplate" version))
(sha256
(base32
- "0vs40ndfyhpx3nj9fc505apk98qgp0pq3cdmqpf67jqkrpcdmnvx"))))
+ "193wwcp84pyyv33pkkm41s7ca2limpcqqi41hxd1pm5il5r9q9h7"))))
(build-system asdf-build-system/sbcl)
(arguments
`(#:phases
--
2.41.0
next reply other threads:[~2023-07-25 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 11:36 André A. Gomes [this message]
2023-07-25 12:12 ` bug#64853: [PATCH]: Update sbcl-nasdf to 0.1.6 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=874jlsz0hp.fsf@gmail.com \
--to=andremegafone@gmail.com \
--cc=64853@debbugs.gnu.org \
--cc=pierre@atlas.engineer \
/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.