From: Trevor Richards <trev@trevdev.ca>
To: 57252@debbugs.gnu.org
Subject: [bug#57252] [PATCH] * gnu/packages/wm.scm (stumpwm-contrib): Update to revision 4
Date: Tue, 16 Aug 2022 15:39:05 -0700 [thread overview]
Message-ID: <3d40a2b07b41c5b67de31435d2ba920d351db894.1660689665.git.trev@trevdev.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
The current revision of stumpwm-contrib is currently more than a year
old now. I am hoping to get a new feature out of
sbcl-stumpwm-screenshot. However, I can't do this without creating
side-effects for all of the stumpwm-contrib child packages.
As an aside it might be a good idea to isolate each child module to its
own commit checkout later on.
---
gnu/packages/wm.scm | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gnu/packages/wm.scm b/gnu/packages/wm.scm
index f4dcbf742e..507c5db92a 100644
--- a/gnu/packages/wm.scm
+++ b/gnu/packages/wm.scm
@@ -1931,8 +1931,8 @@ (define-public stumpwm+slynk
(delete 'cleanup)))))))
(define stumpwm-contrib
- (let ((commit "a7dc1c663d04e6c73a4772c8a6ad56a34381096a")
- (revision "3"))
+ (let ((commit "d0c05077eca5257d33083de949c10bca4aac4242")
+ (revision "4"))
(package
(name "stumpwm-contrib")
(version (git-version "0.0.1" revision commit)) ;no upstream release
@@ -1944,7 +1944,7 @@ (define stumpwm-contrib
(commit commit)))
(file-name (git-file-name name version))
(sha256
- (base32 "09akdaaya7lga5lzbq1aj1filsyjwvflghkidpmr0nk0jz5xx1g7"))))
+ (base32 "0zxhqh9wjfk7zas67kmwfx0a47y8rxmh8f1a5rcs300bv1083lkb"))))
(build-system asdf-build-system/sbcl)
(inputs
`(("stumpwm" ,stumpwm "lib")))
--
2.37.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next reply other threads:[~2022-08-16 22:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 22:39 Trevor Richards [this message]
2022-08-17 8:26 ` bug#57252: [PATCH] * gnu/packages/wm.scm (stumpwm-contrib): Update to revision 4 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=3d40a2b07b41c5b67de31435d2ba920d351db894.1660689665.git.trev@trevdev.ca \
--to=trev@trevdev.ca \
--cc=57252@debbugs.gnu.org \
/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.