From: Guillaume Le Vaillant <glv@posteo.net>
To: "Paul A. Patience" <paul@apatience.com>
Cc: 54938@debbugs.gnu.org
Subject: [bug#54938] [PATCH] gnu: sbcl-py4cl: Update to 0.0.0-1.2f2a008.
Date: Thu, 14 Apr 2022 14:36:27 +0000 [thread overview]
Message-ID: <87fsmfbugj.fsf@kitej> (raw)
In-Reply-To: <20220414140746.34334-1-paul@apatience.com>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
"Paul A. Patience" <paul@apatience.com> skribis:
> * gnu/packages/lisp-xyz.scm (sbcl-py4cl): Update to 0.0.0-1.2f2a008.
> [arguments]<#:phases>: Adjust substitutions to renamed files.
> ---
> gnu/packages/lisp-xyz.scm | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/gnu/packages/lisp-xyz.scm b/gnu/packages/lisp-xyz.scm
> index 29b3a10d98..bd68814aca 100644
> --- a/gnu/packages/lisp-xyz.scm
> +++ b/gnu/packages/lisp-xyz.scm
> @@ -5152,8 +5152,8 @@ (define-public ecl-find-port
> (sbcl-package->ecl-package sbcl-find-port))
>
> (define-public sbcl-py4cl
> - (let ((commit "4c8a2b0814fd311f978964f825ce012290f60136")
> - (revision "1"))
> + (let ((commit "2f2a008dd6162d4446803971292fe1b323fe0dd5")
> + (revision "2"))
> [...]
Hi,
Is there a reason to update only to commit 2f2a008 from September 2019
instead of a more recent one?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-04-14 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 14:07 [bug#54938] [PATCH] gnu: sbcl-py4cl: Update to 0.0.0-1.2f2a008 Paul A. Patience
2022-04-14 14:36 ` Guillaume Le Vaillant [this message]
[not found] ` <-pXFOD8i64LooBxxS-zlALDS97M9U1WyY-kCqpvFQL7WDDO2IKPofQy8PJdzmRlGObTocXAEtgXVgIihw3ugR49OiwS5qZOO-Ez9OKHYynA=@apatience.com>
2022-04-14 18:26 ` [bug#54938] Fw: " Paul A. Patience
2022-04-14 18:35 ` bug#54938: " 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=87fsmfbugj.fsf@kitej \
--to=glv@posteo.net \
--cc=54938@debbugs.gnu.org \
--cc=paul@apatience.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).