[PATCH] gnu: python-pyside-2: Fix qtspeech input name.

  • Done
  • quality assurance status badge
Details
2 participants
  • Guillaume Le Vaillant
  • Jean-Pierre De Jesus DIAZ
Owner
unassigned
Submitted by
Jean-Pierre De Jesus DIAZ
Severity
normal

Debbugs page

J
J
Jean-Pierre De Jesus DIAZ wrote on 9 Apr 03:07 -0700
(address . guix-patches@gnu.org)(name . Jean-Pierre De Jesus DIAZ)(address . jean@foundation.xyz)
06f8f0ba676997c4138e914bae7b7696f87f68da.1712657236.git.jean@foundation.xyz
* gnu/packages/qt.scm (python-pyside-2) <arguments>: Fix input name
of qtspeech-5 on fix-qt-module-detection phase.

Change-Id: Ie566aedddcd03b3b6aedb97dfbea8bc783db2205
---
gnu/packages/qt.scm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

Toggle diff (25 lines)
diff --git a/gnu/packages/qt.scm b/gnu/packages/qt.scm
index dcc9bfeb62..13af841455 100644
--- a/gnu/packages/qt.scm
+++ b/gnu/packages/qt.scm
@@ -30,6 +30,7 @@
;;; Copyright © 2023 Sharlatan Hellseher <sharlatanus@gmail.com>
;;; Copyright © 2022, 2024 Zheng Junjie <873216071@qq.com>
;;; Copyright © 2023 Herman Rimm <herman@rimm.ee>
+;;; Copyright © 2024 Foundation Devices, Inc. <hello@foundation.xyz>
;;;
;;; This file is part of GNU Guix.
;;;
@@ -4842,7 +4843,7 @@ (define-public python-pyside-2
"qtscript"
"qtscxml"
"qtsensors-5"
- "qtspeech-5"
+ "qtspeech"
"qtsvg"
"qttools"
"qtwebchannel"

base-commit: cd45294d576975a3bff2f755764a3f46f09ea6f9
--
2.41.0
G
G
Guillaume Le Vaillant wrote on 9 Apr 04:51 -0700
(name . Jean-Pierre De Jesus DIAZ)(address . jean@foundation.xyz)(address . 70304-done@debbugs.gnu.org)
871q7e92kk.fsf@kitej
Patch applied as 6d0502f9c3608ffd6b3b3c9b603cb5d4ad14d8c9.
Thanks.
-----BEGIN PGP SIGNATURE-----

iIUEAREKAC0WIQTLxZxm7Ce5cXlAaz5r6CCK3yH+PwUCZhUruw8cZ2x2QHBvc3Rl
by5uZXQACgkQa+ggit8h/j9NLQEAobHjloCpGd2iyAAGhmADc4RHWEBc2l1mZBZv
SeT0H94A/jV3BJliBffmymYxkL2mYkWt6pVkAYrOopeujTNPIhpg
=1GV2
-----END PGP SIGNATURE-----

Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 70304@patchwise.org

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