GNU bug report logs - #54938
[PATCH] gnu: sbcl-py4cl: Update to 0.0.0-1.2f2a008.

Previous Next

Full log

View this message in rfc822 format

From: Guillaume Le Vaillant <glv <at> posteo.net>
To: "Paul A. Patience" <paul <at> apatience.com>
Cc: 54938 <at> 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

[Message part 1 (text/plain, inline)]

"Paul A. Patience" <paul <at> 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?

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.