From: kiasoc5 via Guix-patches via <guix-patches@gnu.org>
To: 59428@debbugs.gnu.org
Cc: kiasoc5 <kiasoc5@disroot.org>
Subject: [bug#59428] [PATCH 2/5] gnu: drumkv1: Use qt6 instead of qt5.
Date: Sun, 20 Nov 2022 23:42:32 -0500 [thread overview]
Message-ID: <20221121044235.21227-2-kiasoc5@disroot.org> (raw)
In-Reply-To: <20221121043651.19213-1-kiasoc5@disroot.org>
* gnu/packages/music.scm (drumkv1): Update to 0.9.27.
[inputs]: Remove qtbase-5 and qtsvg-5; add qtbase and qtsvg.
[native-inputs]: Remove qttools-5; add qttools.
---
gnu/packages/music.scm | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gnu/packages/music.scm b/gnu/packages/music.scm
index 2d74c76f49..2507faecc6 100644
--- a/gnu/packages/music.scm
+++ b/gnu/packages/music.scm
@@ -2333,10 +2333,10 @@ (define-public drumkv1
alsa-lib
new-session-manager
liblo
- qtbase-5
- qtsvg-5))
+ qtbase
+ qtsvg))
(native-inputs
- (list pkg-config qttools-5))
+ (list pkg-config qttools))
(home-page "https://drumkv1.sourceforge.io")
(synopsis "Drum-kit sampler synthesizer with stereo effects")
(description
--
2.38.1
next prev parent reply other threads:[~2022-11-21 4:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 4:36 [bug#59428] [PATCH 0/5] Use qt6 instead of qt5 for rncbc's audio projects kiasoc5 via Guix-patches via
2022-11-21 4:42 ` [bug#59428] [PATCH 1/5] gnu: synthv1: Use qt6 instead of qt5 kiasoc5 via Guix-patches via
2022-11-21 4:42 ` kiasoc5 via Guix-patches via [this message]
2022-11-21 4:42 ` [bug#59428] [PATCH 3/5] gnu: samplv1: " kiasoc5 via Guix-patches via
2022-11-21 4:42 ` [bug#59428] [PATCH 4/5] gnu: padthv1: " kiasoc5 via Guix-patches via
2022-11-21 4:42 ` [bug#59428] [PATCH 5/5] gnu: qtractor: " kiasoc5 via Guix-patches via
2022-11-21 14:48 ` [bug#59428] [PATCH 0/5] Use qt6 instead of qt5 for rncbc's audio projects Christopher Baines
2022-11-21 17:01 ` kiasoc5 via Guix-patches via
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=20221121044235.21227-2-kiasoc5@disroot.org \
--to=guix-patches@gnu.org \
--cc=59428@debbugs.gnu.org \
--cc=kiasoc5@disroot.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.