public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/kde:master commit in: www-client/falkon/
Date: Sun, 24 Feb 2019 15:32:45 +0000 (UTC)	[thread overview]
Message-ID: <1551022351.6361925c23ac7d41c8f28aa8f7c89c14253e22f3.asturm@gentoo> (raw)

commit:     6361925c23ac7d41c8f28aa8f7c89c14253e22f3
Author:     Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 24 15:31:46 2019 +0000
Commit:     Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Sun Feb 24 15:32:31 2019 +0000
URL:        https://gitweb.gentoo.org/proj/kde.git/commit/?id=6361925c

www-client/falkon: Fix USE gnome DEPEND

Bug: https://bugs.gentoo.org/678608
Package-Manager: Portage-2.3.62, Repoman-2.3.12
Signed-off-by: Andreas Sturmlechner <asturm <AT> gentoo.org>

 www-client/falkon/falkon-9999.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/www-client/falkon/falkon-9999.ebuild b/www-client/falkon/falkon-9999.ebuild
index c92b2e5f51..99bff646b9 100644
--- a/www-client/falkon/falkon-9999.ebuild
+++ b/www-client/falkon/falkon-9999.ebuild
@@ -31,7 +31,7 @@ COMMON_DEPEND="
 	$(add_qt_dep qtwebengine 'widgets' '' '5=')
 	$(add_qt_dep qtwidgets)
 	dbus? ( $(add_qt_dep qtdbus) )
-	gnome-keyring? ( gnome-base/gnome-keyring )
+	gnome-keyring? ( gnome-base/libgnome-keyring )
 	kde? (
 		$(add_frameworks_dep kcoreaddons)
 		$(add_frameworks_dep kcrash)


             reply	other threads:[~2019-02-24 15:32 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-24 15:32 Andreas Sturmlechner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-29 15:25 [gentoo-commits] proj/kde:master commit in: www-client/falkon/ Andreas Sturmlechner
2024-04-06 20:43 Andreas Sturmlechner
2024-02-27 22:28 Sam James
2023-12-17 21:51 Andreas Sturmlechner
2022-08-15 21:14 Andreas Sturmlechner
2022-02-06 10:49 Andreas Sturmlechner
2022-02-04 14:11 Andreas Sturmlechner
2022-02-02 19:46 Andreas Sturmlechner
2022-02-02 19:46 Andreas Sturmlechner
2022-02-02 19:46 Andreas Sturmlechner
2021-02-25 10:59 Andreas Sturmlechner
2021-02-01 23:45 Andreas Sturmlechner
2019-11-11  0:19 Andreas Sturmlechner
2019-07-15 17:43 Andreas Sturmlechner
2019-04-27 18:27 Andreas Sturmlechner
2019-04-27 18:27 Andreas Sturmlechner
2019-04-27 18:27 Andreas Sturmlechner
2019-03-22 21:38 Andreas Sturmlechner
2019-01-26 23:45 Andreas Sturmlechner
2018-05-09  7:47 Andreas Sturmlechner
2018-05-09  7:43 Andreas Sturmlechner
2018-04-12 18:40 Andreas Sturmlechner
2018-04-12 18:40 Andreas Sturmlechner
2018-04-05 21:57 Andreas Sturmlechner
2018-04-03 15:24 Andreas Sturmlechner
2018-03-17  0:27 Andreas Sturmlechner
2018-03-01 13:20 Andreas Sturmlechner
2018-01-25 19:17 Jimi Huotari
2018-01-25 19:17 Jimi Huotari
2018-01-24 16:45 Andreas Sturmlechner
2017-12-28 10:58 Andreas Sturmlechner
2017-10-23 11:06 Michael Palimaka
2017-10-20 17:50 Andreas Sturmlechner
2017-10-11 16:17 Johannes Huber
2017-10-11 16:14 Johannes Huber
2017-10-08 19:07 Andreas Sturmlechner
2017-10-08 18:09 Andreas Sturmlechner
2017-10-08  8:10 Johannes Huber
2017-10-04 16:47 Andreas Sturmlechner
2017-10-03 21:30 Andreas Sturmlechner

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=1551022351.6361925c23ac7d41c8f28aa8f7c89c14253e22f3.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