public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/nagios-plugins/
Date: Mon, 31 Aug 2015 14:44:07 +0000 (UTC)	[thread overview]
Message-ID: <1441032238.adfb160304979740dcdf284ec05e4e18c0d8c854.mjo@gentoo> (raw)

commit:     adfb160304979740dcdf284ec05e4e18c0d8c854
Author:     Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Mon Aug 31 14:36:59 2015 +0000
Commit:     Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Mon Aug 31 14:43:58 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=adfb1603

net-analyzer/nagios-plugins: revbump to add selinux support.

The plugins have their labels set by sec-policy/selinux-nagios, so
that has been added to RDEPEND (conditional on the new USE
flag). Thanks to Sven Vermeulen for the fix.

Bug: 554964

Package-Manager: portage-2.2.20.1

 net-analyzer/nagios-plugins/metadata.xml                             | 5 +++++
 .../{nagios-plugins-2.1.1.ebuild => nagios-plugins-2.1.1-r1.ebuild}  | 5 +++--
 2 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/net-analyzer/nagios-plugins/metadata.xml b/net-analyzer/nagios-plugins/metadata.xml
index 924971a..89d2fa5 100644
--- a/net-analyzer/nagios-plugins/metadata.xml
+++ b/net-analyzer/nagios-plugins/metadata.xml
@@ -11,6 +11,11 @@
       <name>Chris Reffett</name>
       <description>Proxy maintainer. CC him on bugs.</description>
   </maintainer>
+  <maintainer>
+      <email>mjo@gentoo.org</email>
+      <name>Michael Orlitzky</name>
+      <description>Maintainer. CC him on bugs.</description>
+  </maintainer>
   <herd>proxy-maintainers</herd>
   <herd>sysadmin</herd>
   <use>

diff --git a/net-analyzer/nagios-plugins/nagios-plugins-2.1.1.ebuild b/net-analyzer/nagios-plugins/nagios-plugins-2.1.1-r1.ebuild
similarity index 96%
rename from net-analyzer/nagios-plugins/nagios-plugins-2.1.1.ebuild
rename to net-analyzer/nagios-plugins/nagios-plugins-2.1.1-r1.ebuild
index eb1b93e..f2d543f 100644
--- a/net-analyzer/nagios-plugins/nagios-plugins-2.1.1.ebuild
+++ b/net-analyzer/nagios-plugins/nagios-plugins-2.1.1-r1.ebuild
@@ -13,7 +13,7 @@ SRC_URI="http://nagios-plugins.org/download/${P}.tar.gz"
 LICENSE="GPL-2"
 SLOT="0"
 KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~sparc ~x86"
-IUSE="ipv6 ldap mysql nagios-dns nagios-ping nagios-game postgres samba snmp ssh +ssl"
+IUSE="ipv6 ldap mysql nagios-dns nagios-ping nagios-game postgres samba selinux snmp ssh +ssl"
 
 # Most of the plugins use automagic dependencies, i.e. the plugin will
 # get built if the binary it uses is installed. For example, check_snmp
@@ -41,7 +41,8 @@ DEPEND="${REAL_DEPEND}
 
 # Basically everything collides with nagios-plugins.
 RDEPEND="${DEPEND}
-	!net-analyzer/monitoring-plugins"
+	!net-analyzer/monitoring-plugins
+	selinux? ( sec-policy/selinux-nagios )"
 
 # At least one test is interactive.
 RESTRICT="test"


             reply	other threads:[~2015-08-31 14:44 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 14:44 Michael Orlitzky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-18  3:00 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/nagios-plugins/ Michael Orlitzky
2025-02-23 15:17 Michael Orlitzky
2025-02-23  3:09 Sam James
2025-02-16  6:32 Sam James
2025-02-16  6:32 Sam James
2025-02-16  6:32 Sam James
2024-11-14 23:30 Michael Orlitzky
2024-02-18 22:42 Sam James
2024-02-18 19:57 Arthur Zamarin
2024-02-18 19:57 Arthur Zamarin
2024-02-18 19:57 Arthur Zamarin
2024-02-18 15:10 Michael Orlitzky
2024-02-18 15:10 Michael Orlitzky
2023-09-09 23:44 Michael Orlitzky
2023-05-11 20:03 Sam James
2023-01-28  9:06 Sam James
2023-01-28  9:02 Arthur Zamarin
2023-01-28  8:54 Sam James
2023-01-28  8:54 Sam James
2022-12-01  0:35 Michael Orlitzky
2022-12-01  0:26 Michael Orlitzky
2022-12-01  0:19 Michael Orlitzky
2022-12-01  0:08 Michael Orlitzky
2022-11-30 23:30 Michael Orlitzky
2022-11-19 23:06 Michael Orlitzky
2022-08-30  1:05 Michael Orlitzky
2022-08-29 12:38 Jakov Smolić
2022-08-12 14:27 Sam James
2022-08-06 13:04 Michael Orlitzky
2022-08-03 17:51 Arthur Zamarin
2022-08-03 16:12 Arthur Zamarin
2022-06-02 17:23 Michael Orlitzky
2022-03-23  0:45 Sam James
2021-06-22 18:19 Sam James
2021-05-01 10:02 Mikle Kolyada
2021-03-22  2:56 Michael Orlitzky
2020-11-30 16:17 Aaron Bauman
2020-08-05 15:34 Michael Orlitzky
2020-08-01  9:01 Sergei Trofimovich
2020-08-01  8:53 Sergei Trofimovich
2020-07-28 21:25 Sergei Trofimovich
2020-07-27 18:36 Sergei Trofimovich
2020-07-24 15:09 Agostino Sarubbo
2020-07-23 16:51 Michael Orlitzky
2020-01-17 17:02 Michael Orlitzky
2019-12-11 16:26 Michael Orlitzky
2019-12-11 15:26 Michael Orlitzky
2019-08-31 21:35 Michael Orlitzky
2019-02-16 16:01 Michael Orlitzky
2019-01-31 18:04 Tobias Klausmann
2019-01-29 17:12 Mikle Kolyada
2019-01-24 22:22 Thomas Deutschmann
2019-01-24 21:43 Sergei Trofimovich
2019-01-23 21:12 Sergei Trofimovich
2019-01-23 21:01 Sergei Trofimovich
2019-01-23 19:29 Sergei Trofimovich
2018-09-23  1:27 Michael Orlitzky
2018-06-19 12:55 Thomas Deutschmann
2018-03-03 21:07 Sergei Trofimovich
2017-12-16  8:20 Tobias Klausmann
2017-11-25 20:59 Sergei Trofimovich
2017-11-18 17:59 Sergei Trofimovich
2017-11-17 11:18 Tobias Klausmann
2017-11-15  2:16 Michael Orlitzky
2017-10-22 19:59 Michael Orlitzky
2017-07-23 14:05 Michael Orlitzky
2017-03-30 22:14 Michael Orlitzky
2016-12-11 17:11 Michael Orlitzky
2016-12-11 17:11 Michael Orlitzky
2016-08-07  0:40 Michael Orlitzky
2015-10-05 13:52 Julian Ospald
2015-08-31 14:13 Michael Orlitzky

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=1441032238.adfb160304979740dcdf284ec05e4e18c0d8c854.mjo@gentoo \
    --to=mjo@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