From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-cluster/corosync/
Date: Wed, 28 Jun 2023 07:55:14 +0000 (UTC) [thread overview]
Message-ID: <1687938902.c683b3348cc8e55b8305912ca64aaa4ee24a04c1.sam@gentoo> (raw)
commit: c683b3348cc8e55b8305912ca64aaa4ee24a04c1
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Jun 28 07:54:06 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Jun 28 07:55:02 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c683b334
sys-cluster/corosync: add missing selinux policy dep
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-cluster/corosync/corosync-3.1.0.ebuild | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/sys-cluster/corosync/corosync-3.1.0.ebuild b/sys-cluster/corosync/corosync-3.1.0.ebuild
index 9994b075c484..614f1d632a1e 100644
--- a/sys-cluster/corosync/corosync-3.1.0.ebuild
+++ b/sys-cluster/corosync/corosync-3.1.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2022 Gentoo Authors
+# Copyright 1999-2023 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=7
@@ -12,9 +12,10 @@ SRC_URI="https://github.com/${PN}/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="BSD-2 public-domain"
SLOT="0"
KEYWORDS="amd64 ~arm ~arm64 ~hppa ~ppc ppc64 x86"
-IUSE="augeas dbus doc snmp systemd watchdog xml"
+IUSE="augeas dbus doc selinux snmp systemd watchdog xml"
-RDEPEND="dev-libs/nss
+DEPEND="
+ dev-libs/nss
>=sys-cluster/libqb-2.0.0:=
sys-cluster/kronosnet:=
augeas? ( app-admin/augeas )
@@ -22,8 +23,11 @@ RDEPEND="dev-libs/nss
snmp? ( net-analyzer/net-snmp )
systemd? ( sys-apps/systemd:= )
watchdog? ( sys-kernel/linux-headers )
- "
-DEPEND="${RDEPEND}"
+"
+RDEPEND="
+ ${DEPEND}
+ selinux? ( sec-policy/selinux-corosync )
+"
BDEPEND="virtual/pkgconfig
doc? ( sys-apps/groff )"
next reply other threads:[~2023-06-28 7:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 7:55 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-17 6:27 [gentoo-commits] repo/gentoo:master commit in: sys-cluster/corosync/ Ionen Wolkens
2024-01-12 8:30 Arthur Zamarin
2021-02-03 20:19 Thomas Deutschmann
2021-01-15 22:07 Sam James
2021-01-14 23:59 Sam James
2021-01-10 21:58 Sam James
2021-01-09 6:56 Sam James
2021-01-01 23:29 Sam James
2020-12-01 21:55 Marc Schiffbauer
2020-11-23 16:39 Sergei Trofimovich
2020-11-12 17:17 Marc Schiffbauer
2020-11-12 17:10 Marc Schiffbauer
2020-10-21 12:59 Alexys Jacob
2020-07-20 12:24 Sam James
2020-05-05 21:46 Sergei Trofimovich
2020-04-28 8:52 Mikle Kolyada
2019-11-24 3:36 Aaron Bauman
2019-08-11 8:45 Michał Górny
2018-04-15 14:30 Johannes Huber
2018-04-14 19:33 Mikle Kolyada
2018-02-22 9:05 Agostino Sarubbo
2018-02-06 15:10 Thomas Deutschmann
2017-12-03 21:11 Sergei Trofimovich
2017-06-19 16:52 Alexis Ballier
2017-06-19 16:33 Alexis Ballier
2017-05-30 15:34 Lars Wendler
2017-05-19 1:10 Michael Weber
2017-05-16 13:05 Agostino Sarubbo
2017-05-16 8:01 Agostino Sarubbo
2017-05-11 14:41 Agostino Sarubbo
2017-04-22 15:05 Alexys Jacob
2017-02-23 9:20 Michael Weber
2017-02-23 8:34 Michael Weber
2016-06-29 22:33 Alexey Shvetsov
2016-03-09 11:29 Alexys Jacob
2016-01-26 8:25 Alexys Jacob
2015-09-06 4:18 Doug Goldstein
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=1687938902.c683b3348cc8e55b8305912ca64aaa4ee24a04c1.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