From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-gfx/photoqt/
Date: Tue, 06 May 2025 19:20:02 +0000 (UTC) [thread overview]
Message-ID: <1746558556.92f6f35297854f8764873d1befd11b630df5c3d8.sam@gentoo> (raw)
commit: 92f6f35297854f8764873d1befd11b630df5c3d8
Author: Nicolas PARLANT <nicolas.parlant <AT> parhuet <DOT> fr>
AuthorDate: Tue May 6 13:49:25 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue May 6 19:09:16 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=92f6f352
media-gfx/photoqt: add missing PYTHON_USEDEP on dev-python/pychromecast
Package try to import pychromecast while configuring.
Thus it can't be installed with a mismatch target, so norevbump.
Signed-off-by: Nicolas PARLANT <nicolas.parlant <AT> parhuet.fr>
Part-of: https://github.com/gentoo/gentoo/pull/41959
Signed-off-by: Sam James <sam <AT> gentoo.org>
media-gfx/photoqt/photoqt-4.8.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/media-gfx/photoqt/photoqt-4.8.1.ebuild b/media-gfx/photoqt/photoqt-4.8.1.ebuild
index 49a3b7f9a6ab..74307d71a630 100644
--- a/media-gfx/photoqt/photoqt-4.8.1.ebuild
+++ b/media-gfx/photoqt/photoqt-4.8.1.ebuild
@@ -28,7 +28,7 @@ COMMON_DEPEND="
barcode? ( media-libs/zxing-cpp:= )
chromecast? (
${PYTHON_DEPS}
- $(python_gen_cond_dep 'dev-python/pychromecast')
+ $(python_gen_cond_dep 'dev-python/pychromecast[${PYTHON_USEDEP}]')
)
devil? ( media-libs/devil )
exif? ( media-gfx/exiv2:=[bmff] )
next reply other threads:[~2025-05-06 19:20 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 19:20 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-07 11:58 [gentoo-commits] repo/gentoo:master commit in: media-gfx/photoqt/ Petr Vaněk
2025-08-18 1:53 Sam James
2025-06-30 12:53 Petr Vaněk
2025-06-17 17:49 Sam James
2025-05-06 19:20 Sam James
2025-05-06 19:20 Sam James
2025-04-29 19:31 Sam James
2025-04-29 19:31 Sam James
2025-04-26 17:12 Arthur Zamarin
2025-04-24 22:29 Sam James
2025-03-24 5:26 Sam James
2025-03-24 5:26 Sam James
2025-01-31 8:28 Joonas Niilola
2025-01-08 8:22 Ionen Wolkens
2025-01-07 22:34 Andreas Sturmlechner
2025-01-07 22:34 Andreas Sturmlechner
2023-11-14 22:55 Andreas Sturmlechner
2023-06-16 22:59 Sam James
2023-06-16 21:02 Sam James
2023-05-15 23:16 Sam James
2023-05-15 21:42 Andreas Sturmlechner
2023-01-25 19:22 Arthur Zamarin
2023-01-20 3:54 Sam James
2022-10-25 17:55 Sam James
2022-10-25 17:55 Sam James
2022-09-24 7:16 Andreas Sturmlechner
2022-09-23 20:07 Andreas Sturmlechner
2019-12-09 12:26 Andreas Sturmlechner
2019-03-17 13:22 Andreas Sturmlechner
2019-02-15 20:10 Andreas Sturmlechner
2019-02-15 17:09 Mikle Kolyada
2019-02-15 0:18 Thomas Deutschmann
2019-01-16 15:12 Mikle Kolyada
2018-12-31 16:43 Thomas Deutschmann
2018-12-30 13:22 Andreas Sturmlechner
2018-12-29 22:02 Andreas Sturmlechner
2018-06-30 2:37 Michael Palimaka
2018-01-12 10:45 Michael Palimaka
2017-07-02 3:04 Michael Palimaka
2017-04-27 12:17 Michael Palimaka
2017-04-26 7:40 Agostino Sarubbo
2017-01-22 16:14 Michael Palimaka
2016-08-11 17:05 Michael Palimaka
2016-08-11 17:05 Michael Palimaka
2016-08-11 17:05 Michael Palimaka
2016-07-08 18:38 Michael Palimaka
2016-07-08 18:38 Michael Palimaka
2016-05-26 12:22 Michael Palimaka
2016-05-26 12:22 Michael Palimaka
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=1746558556.92f6f35297854f8764873d1befd11b630df5c3d8.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox