[PATCH] gnu: cl-tooter: Update to 1.0.0.2e1b22f05.

  • Done
  • quality assurance status badge
Details
2 participants
  • cage
  • Guillaume Le Vaillant
Owner
unassigned
Submitted by
cage
Severity
normal
C
(address . guix-patches@gnu.org)
b0452185cf15a7f74ff97b2141320e90c77fab46.1691230175.git.cage-dev@twistfold.it
---
gnu/packages/lisp-xyz.scm | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

Toggle diff (26 lines)
diff --git a/gnu/packages/lisp-xyz.scm b/gnu/packages/lisp-xyz.scm
index d2596ebc2d..9123923603 100644
--- a/gnu/packages/lisp-xyz.scm
+++ b/gnu/packages/lisp-xyz.scm
@@ -18552,8 +18552,8 @@ (define-public cl-html-diff
(sbcl-package->cl-source-package sbcl-cl-html-diff))

(define-public sbcl-tooter
- (let ((commit "ec97bee3431c55913078e532daae81eb0fd90372")
- (revision "3"))
+ (let ((commit "2e1b22f0993419c1e7e6d10ead45d7bcafb5b6cb")
+ (revision "4"))
(package
(name "sbcl-tooter")
(version (git-version "1.0.0" revision commit))
@@ -18565,7 +18565,7 @@ (define-public sbcl-tooter
(commit commit)))
(file-name (git-file-name "tooter" version))
(sha256
- (base32 "02vpjaq38d6laaqmsana9f13c38xzr0xwy05fcfkmzdhh0kllpkv"))))
+ (base32 "02ys58gzasvk7r84jmz6k522qcw2hkbgv8p0ax5i8dggjhr04cz2"))))
(build-system asdf-build-system/sbcl)
(inputs
(list sbcl-cl-ppcre sbcl-documentation-utils sbcl-drakma

base-commit: 42ae42cf41e8f5e88422e30d801251a3427d7f3b
--
2.34.0
G
G
Guillaume Le Vaillant wrote on 8 Aug 2023 10:32
(name . cage)(address . cage-dev@twistfold.it)(address . 65086-done@debbugs.gnu.org)
87tttakk7c.fsf@kitej
Patch pushed as c7d9fb58a76d38356c8f9b06c17f9085a3fef968 with a complete
commit message.
Thanks.
-----BEGIN PGP SIGNATURE-----

iIUEAREKAC0WIQTLxZxm7Ce5cXlAaz5r6CCK3yH+PwUCZNH9tw8cZ2x2QHBvc3Rl
by5uZXQACgkQa+ggit8h/j9HOwEAjCyJjJEOpfHflyJalpGGgHGZMjQiscQJupjn
X3RnkvwA/iS4OMsQe/t28ILEYlk9hp7Xzqrxig5xZ0N0Q1V3YD4u
=zFnV
-----END PGP SIGNATURE-----

Closed
?
Your comment

This issue is archived.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 65086
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