From: "Jason Zaman" <perfinion@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gnome-base/gnome-keyring/
Date: Mon, 31 Oct 2016 13:12:09 +0000 (UTC) [thread overview]
Message-ID: <1477919481.d3936df28c4bf3183738d923710c69a7dc896bec.perfinion@gentoo> (raw)
commit: d3936df28c4bf3183738d923710c69a7dc896bec
Author: Jason Zaman <perfinion <AT> gentoo <DOT> org>
AuthorDate: Mon Oct 31 12:47:03 2016 +0000
Commit: Jason Zaman <perfinion <AT> gentoo <DOT> org>
CommitDate: Mon Oct 31 13:11:21 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d3936df2
gnome-base/gnome-keyring: Add selinux policy dep
Package-Manager: portage-2.3.0
gnome-base/gnome-keyring/gnome-keyring-3.20.0.ebuild | 1 +
1 file changed, 1 insertion(+)
diff --git a/gnome-base/gnome-keyring/gnome-keyring-3.20.0.ebuild b/gnome-base/gnome-keyring/gnome-keyring-3.20.0.ebuild
index 76321f3..c1c5e52 100644
--- a/gnome-base/gnome-keyring/gnome-keyring-3.20.0.ebuild
+++ b/gnome-base/gnome-keyring/gnome-keyring-3.20.0.ebuild
@@ -24,6 +24,7 @@ RDEPEND="
>=dev-libs/libgcrypt-1.2.2:0=
caps? ( sys-libs/libcap-ng )
pam? ( virtual/pam )
+ selinux? ( sec-policy/selinux-gnome )
>=app-crypt/gnupg-2.0.28:=
"
DEPEND="${RDEPEND}
next reply other threads:[~2016-10-31 13:12 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 13:12 Jason Zaman [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-17 9:24 [gentoo-commits] repo/gentoo:master commit in: gnome-base/gnome-keyring/ Pacho Ramos
2024-07-17 9:24 Pacho Ramos
2024-07-17 9:24 Pacho Ramos
2024-06-06 0:45 Sam James
2024-06-06 0:45 Sam James
2023-05-14 17:11 Sam James
2023-05-14 8:12 Sam James
2022-10-30 16:34 Matt Turner
2022-10-29 17:44 Matt Turner
2022-10-01 17:16 Matt Turner
2022-07-21 0:13 Sam James
2022-07-18 23:41 Sam James
2022-07-18 17:44 Sam James
2022-05-23 19:45 Matt Turner
2022-05-23 19:45 Matt Turner
2022-05-23 19:45 Matt Turner
2022-05-18 8:00 WANG Xuerui
2022-03-25 21:47 Matt Turner
2022-01-24 19:21 Sam James
2022-01-24 14:49 Sam James
2022-01-24 14:45 Sam James
2022-01-20 9:42 Arthur Zamarin
2021-09-29 12:11 Mart Raudsepp
2021-05-28 19:18 Sam James
2021-05-26 15:16 Yixun Lan
2021-04-16 3:41 Matt Turner
2021-01-18 21:10 Matt Turner
2020-11-06 15:19 Sam James
2020-11-06 6:57 Sam James
2020-11-05 16:16 Sam James
2020-09-24 14:24 Pacho Ramos
2020-09-19 19:19 Pacho Ramos
2020-09-19 15:53 Michał Górny
2020-08-31 2:52 Sam James
2020-08-30 18:28 Sam James
2020-07-29 4:49 Sam James
2020-07-27 7:22 Mart Raudsepp
2020-06-07 21:02 Mart Raudsepp
2020-04-22 14:25 Agostino Sarubbo
2020-04-22 8:44 Agostino Sarubbo
2020-04-22 8:41 Agostino Sarubbo
2020-03-17 21:32 Mart Raudsepp
2020-01-11 12:10 Mart Raudsepp
2020-01-11 12:10 Mart Raudsepp
2020-01-01 15:25 Agostino Sarubbo
2019-12-09 9:14 Agostino Sarubbo
2019-12-09 9:11 Agostino Sarubbo
2019-12-09 0:10 Aaron Bauman
2019-12-08 11:59 Mikle Kolyada
2019-12-08 11:58 Mikle Kolyada
2019-10-12 21:38 Mart Raudsepp
2019-10-12 19:30 Mikle Kolyada
2019-10-09 8:27 Agostino Sarubbo
2019-05-21 3:17 Aaron Bauman
2019-03-02 14:28 Mart Raudsepp
2019-02-17 16:01 Mikle Kolyada
2018-12-28 3:46 Matt Turner
2018-10-29 1:01 Matt Turner
2018-10-27 18:43 Sergei Trofimovich
2018-10-26 20:19 Sergei Trofimovich
2018-09-23 8:47 Mart Raudsepp
2018-09-22 19:54 Mart Raudsepp
2017-12-27 8:35 Markus Meier
2017-12-19 19:14 Thomas Deutschmann
2017-11-18 13:20 Sergei Trofimovich
2017-11-06 20:49 Tobias Klausmann
2017-11-04 13:04 Sergei Trofimovich
2017-07-09 22:14 Mart Raudsepp
2016-12-06 20:29 Markus Meier
2016-07-30 10:27 Jeroen Roovers
2016-06-08 19:56 Markus Meier
2016-06-07 7:03 Tobias Klausmann
2016-05-29 12:47 Pacho Ramos
2016-05-03 20:15 Markus Meier
2016-03-06 17:23 Mikle Kolyada
2015-11-26 10:51 Gilles Dartiguelongue
2015-11-16 14:08 Agostino Sarubbo
2015-10-18 11:29 Mikle Kolyada
2015-10-03 8:35 Markus Meier
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=1477919481.d3936df28c4bf3183738d923710c69a7dc896bec.perfinion@gentoo \
--to=perfinion@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