From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/kde:master commit in: net-irc/konversation/
Date: Sat, 9 Nov 2024 10:55:59 +0000 (UTC) [thread overview]
Message-ID: <1731147875.cd32469153536006b509c00330d4dca147607454.asturm@gentoo> (raw)
commit: cd32469153536006b509c00330d4dca147607454
Author: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 9 10:24:35 2024 +0000
Commit: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Sat Nov 9 10:24:35 2024 +0000
URL: https://gitweb.gentoo.org/proj/kde.git/commit/?id=cd324691
net-irc/konversation: Prepare for app-crypt/qca to drop IUSE qt6
Signed-off-by: Andreas Sturmlechner <asturm <AT> gentoo.org>
net-irc/konversation/konversation-9999.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-irc/konversation/konversation-9999.ebuild b/net-irc/konversation/konversation-9999.ebuild
index 1a51c95c99..e34da7fb0f 100644
--- a/net-irc/konversation/konversation-9999.ebuild
+++ b/net-irc/konversation/konversation-9999.ebuild
@@ -50,7 +50,7 @@ DEPEND="
"
RDEPEND="${DEPEND}
>=dev-qt/qtsvg-${QTMIN}:6
- crypt? ( >=app-crypt/qca-2.3.7:2[qt6,ssl] )
+ crypt? ( >=app-crypt/qca-2.3.7:2[qt6(+),ssl] )
"
BDEPEND="sys-devel/gettext"
next reply other threads:[~2024-11-09 10:56 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 10:55 Andreas Sturmlechner [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-07 8:41 [gentoo-commits] proj/kde:master commit in: net-irc/konversation/ Andreas Sturmlechner
2024-02-27 22:28 Sam James
2024-01-18 0:26 Sam James
2024-01-09 14:26 Andreas Sturmlechner
2022-03-24 14:53 Andreas Sturmlechner
2020-10-26 13:56 Andreas Sturmlechner
2020-10-18 16:01 Andreas Sturmlechner
2020-09-28 21:26 Andreas Sturmlechner
2020-07-10 13:28 Andreas Sturmlechner
2019-11-13 2:00 Andreas Sturmlechner
2018-10-13 16:34 Andreas Sturmlechner
2018-02-22 13:17 Andreas Sturmlechner
2017-11-09 21:15 Andreas Sturmlechner
2017-04-15 4:43 Michael Palimaka
2017-03-30 23:33 Andreas Sturmlechner
2016-07-25 17:16 Michael Palimaka
2016-07-22 18:01 Michael Palimaka
2016-07-22 18:01 Michael Palimaka
2016-05-17 19:43 Johannes Huber
2016-04-08 16:43 Johannes Huber
2016-03-21 18:01 Johannes Huber
2015-06-02 21:36 Johannes Huber
2015-06-02 21:36 Johannes Huber
2015-04-23 15:57 Manuel Rüger
2015-01-29 1:24 Johannes Huber
2015-01-20 20:34 Johannes Huber
2014-11-25 15:13 Michael Palimaka
2014-11-13 8:44 Michael Palimaka
2014-10-14 14:00 Michael Palimaka
2014-10-12 18:11 Michael Palimaka
2014-09-13 17:44 Michael Palimaka
2014-09-11 17:16 Michael Palimaka
2014-08-17 15:16 Johannes Huber
2014-07-15 16:58 Michael Palimaka
2014-07-15 16:56 Michael Palimaka
2014-07-15 16:49 Michael Palimaka
2014-07-15 16:45 Michael Palimaka
2014-07-15 16:43 Michael Palimaka
2014-07-15 16:38 Michael Palimaka
2014-07-15 16:35 Michael Palimaka
2014-07-15 16:35 Michael Palimaka
2014-07-15 16:33 Michael Palimaka
2014-07-15 16:33 Michael Palimaka
2014-07-12 23:49 David Heidelberger
2013-06-01 19:59 Tomas Chvatal
2013-04-25 19:29 Johannes Huber
2013-04-06 1:46 Manuel Rüger
2012-08-22 20:12 Johannes Huber
2011-12-08 10:40 Johannes Huber
2011-12-05 21:17 Johannes Huber
2011-12-02 13:04 Johannes Huber
2011-03-16 9:57 Tomas Chvatal
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=1731147875.cd32469153536006b509c00330d4dca147607454.asturm@gentoo \
--to=asturm@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