[PATCH] gnu: guile-smc: Update to 0.6.1

  • Done
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • Artyom V. Poptsov
Owner
unassigned
Submitted by
Artyom V. Poptsov
Severity
normal
A
A
Artyom V. Poptsov wrote on 8 Aug 2023 21:37
(address . guix-patches@gnu.org)
87r0od2um9.fsf@gmail.com
Hello,

this patch updates Guile-SMC[1] to 0.6.1.
From f4b166610e44beaa9ba1a1d9cbe8fc2e8c3a8cf2 Mon Sep 17 00:00:00 2001
Message-Id: <f4b166610e44beaa9ba1a1d9cbe8fc2e8c3a8cf2.1691523172.git.poptsov.artyom@gmail.com>
From: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>
Date: Tue, 8 Aug 2023 22:32:39 +0300
Subject: [PATCH] gnu: guile-smc: Update to 0.6.1.

* gnu/packages/guile-xyz.scm (guile-smc): Update to 0.6.1.
---
gnu/packages/guile-xyz.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Toggle diff (26 lines)
diff --git a/gnu/packages/guile-xyz.scm b/gnu/packages/guile-xyz.scm
index a350b6700e..d90ff16794 100644
--- a/gnu/packages/guile-xyz.scm
+++ b/gnu/packages/guile-xyz.scm
@@ -5345,7 +5345,7 @@ (define-public guile-gitlab
(define-public guile-smc
(package
(name "guile-smc")
- (version "0.6.0")
+ (version "0.6.1")
(source
(origin
(method git-fetch)
@@ -5355,7 +5355,7 @@ (define-public guile-smc
(file-name (string-append name "-" version))
(sha256
(base32
- "15b8m30kjl46p44xjd65vv1bv60hy130zfskkcsrj10fzahyk9zd"))))
+ "02729gkywzimmdlmnwzclvs3wl92f9mvp5dmcbp75kmwibxly288"))))
(build-system gnu-build-system)
(arguments
`(#:make-flags '("GUILE_AUTO_COMPILE=0") ;to prevent guild warnings

base-commit: 4547bc6fa3142dca77f7fc912368aeff31bd6e53
--
2.34.1
- Artyom

References:

--
Artyom "avp" Poptsov <poptsov.artyom@gmail.com>
CADR Hackerspace co-founder: https://cadrspace.ru/
GPG: D0C2 EAC1 3310 822D 98DE B57C E9C5 A2D9 0898 A02F
-----BEGIN PGP SIGNATURE-----

iQFNBAEBCgA3FiEE0MLqwTMQgi2Y3rV86cWi2QiYoC8FAmTSmX4ZHHBvcHRzb3Yu
YXJ0eW9tQGdtYWlsLmNvbQAKCRDpxaLZCJigL8A2CACpN6Q1fqsjc4/TmjZy6mP2
phcFIx0TrtOzdI/SY1PBYIRHGEaVIGHD8pCF9EsN3FowkkI7Fz2s3xZ3OZQZgLBc
z3kzB0qpk9jcULSV6u1bvFXIMpxLoCsg3WOUHoT7+jquBTDwUtjHkgFRuF+Rl9YX
DLE76WYmqBW7d00U0aLXsJqfjAoWe2w8vkayW4e7Mu/JQ4bd7IdQ6WmpcIX8LPU0
Jhywml+LBiqC2QChKGKX/5Mb9KFoSShodh0eSNGD3jeq+KD2VJYHs5j9X5Mnk+Lb
kYlN0OFDGdo1Cw3UUsclQdAAnBrvlqaFZcAPjukemeR8K4uV5TXoeaUjj7xBPyUL
=+Bq+
-----END PGP SIGNATURE-----

L
L
Ludovic Courtès wrote on 12 Aug 2023 23:04
(name . Artyom V. Poptsov)(address . poptsov.artyom@gmail.com)(address . 65158-done@debbugs.gnu.org)
87ttt4c6r6.fsf@gnu.org
Hi,

"Artyom V. Poptsov" <poptsov.artyom@gmail.com> skribis:

Toggle quote (8 lines)
> From f4b166610e44beaa9ba1a1d9cbe8fc2e8c3a8cf2 Mon Sep 17 00:00:00 2001
> Message-Id: <f4b166610e44beaa9ba1a1d9cbe8fc2e8c3a8cf2.1691523172.git.poptsov.artyom@gmail.com>
> From: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>
> Date: Tue, 8 Aug 2023 22:32:39 +0300
> Subject: [PATCH] gnu: guile-smc: Update to 0.6.1.
>
> * gnu/packages/guile-xyz.scm (guile-smc): Update to 0.6.1.

Applied, thanks!

Ludo’.
Closed
A
A
Artyom V. Poptsov wrote on 13 Aug 2023 08:43
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 65158-done@debbugs.gnu.org)
87bkfb5tno.fsf@gmail.com
Hello Ludovic!

Thank you for applying the patch that updates Guile-SMC to 0.6.1!

But there's a pending patch for 0.6.2 already:

:-)

- Artyom

--
Artyom "avp" Poptsov <poptsov.artyom@gmail.com>
CADR Hackerspace co-founder: https://cadrspace.ru/
GPG: D0C2 EAC1 3310 822D 98DE B57C E9C5 A2D9 0898 A02F
-----BEGIN PGP SIGNATURE-----

iQFNBAEBCgA3FiEE0MLqwTMQgi2Y3rV86cWi2QiYoC8FAmTYe5sZHHBvcHRzb3Yu
YXJ0eW9tQGdtYWlsLmNvbQAKCRDpxaLZCJigLyMtCACpGzUJkML2y/eYGrrovfaT
hICtCdXVKYIBcOkV/9sneOKE8OmLdaQnutA+Q/GylfCD7mZIEWFf65r/hiIVtpXs
3DkStjWDqKl1NGQJKouwJ0V20CFQgaUh7X6uD3AB4kW1mwJI00elKUfeno+QNFvX
Ej2ch5ZUwJGXqr9gslJoalD1Rml5TOZV1dYb9wwrK+euSJ+2+LeaUMyqBJsGTJc1
wDxxkWODvxqqLIDWiVQ7bGvzsqcs1gjvSHWIpM6XkypbJtjtbaPtGhK9BjJIRfNj
bbo96xopAOZxzR9VlNQGBrYykm73vz1YB/3pWNTDt5cu+6pe9rmIA3+XbE9LhOyS
=xkVY
-----END PGP SIGNATURE-----

Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 65158@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 65158
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch