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/monitoring-plugins/
Date: Wed, 26 Jun 2024 11:36:53 +0000 (UTC)	[thread overview]
Message-ID: <1719400862.f80b374043945c811c758e13516f1c9f98f1fe3f.mjo@gentoo> (raw)

commit:     f80b374043945c811c758e13516f1c9f98f1fe3f
Author:     NHOrus <jy6x2b32pie9 <AT> yahoo <DOT> com>
AuthorDate: Wed Jun 26 06:25:37 2024 +0000
Commit:     Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Wed Jun 26 11:21:02 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f80b3740

net-analyzer/monitoring-plugins: drop 2.3.3-r2

We have 2.3.5 that fixed those errors and is stable.

Closes: https://bugs.gentoo.org/871519
Closes: https://bugs.gentoo.org/892471
Closes: https://github.com/gentoo/gentoo/pull/37306
Signed-off-by: NHOrus <jy6x2b32pie9 <AT> yahoo.com>
Signed-off-by: Michael Orlitzky <mjo <AT> gentoo.org>

 net-analyzer/monitoring-plugins/Manifest           |   1 -
 .../monitoring-plugins-2.3.3-r2.ebuild             | 110 ---------------------
 2 files changed, 111 deletions(-)

diff --git a/net-analyzer/monitoring-plugins/Manifest b/net-analyzer/monitoring-plugins/Manifest
index 545a0d98a9f7..db1a7cbc1868 100644
--- a/net-analyzer/monitoring-plugins/Manifest
+++ b/net-analyzer/monitoring-plugins/Manifest
@@ -1,2 +1 @@
-DIST monitoring-plugins-2.3.3.tar.gz 2620192 BLAKE2B 47bd7e71cf470781bb3bd8c8437ebfccdc977e48a3eba1d83ba85c2c1a8c154c7db832e3bb7189bf669083a10069c7fe09c7235a00b35fd9a6d80afcdbb44246 SHA512 502274b47da2ad04d0e2e4e29baa7e5ad8b9a9ece36794dcdf7dfcc087de30e514ff6937eaaa26b93daad329fcd11b72c3c87cad826e6bf6bafffa450077706f
 DIST monitoring-plugins-2.3.5.tar.gz 2876130 BLAKE2B 7029f6485ef73d29329bcb36e16cbbaa99c57ae20505f554af154b45cc1af6f623dabb35ee5b7f777d728bcae8eafd795f12aabc199cf1f45c9f2335f74b6d41 SHA512 bb04d547584a4aed82bfd605d129b652b45c7356c0610fb1da53a57b2ab889b67afccdd53998e2612ec06571bdc5fc238ef0d378b96e29ec072f657e74eabd55

diff --git a/net-analyzer/monitoring-plugins/monitoring-plugins-2.3.3-r2.ebuild b/net-analyzer/monitoring-plugins/monitoring-plugins-2.3.3-r2.ebuild
deleted file mode 100644
index e364f28aa4cc..000000000000
--- a/net-analyzer/monitoring-plugins/monitoring-plugins-2.3.3-r2.ebuild
+++ /dev/null
@@ -1,110 +0,0 @@
-# Copyright 1999-2023 Gentoo Authors
-# Distributed under the terms of the GNU General Public License v2
-
-EAPI="8"
-
-inherit flag-o-matic
-
-DESCRIPTION="50+ standard plugins for Icinga, Naemon, Nagios, Shinken, Sensu"
-HOMEPAGE="https://www.monitoring-plugins.org/"
-SRC_URI="https://www.monitoring-plugins.org/download/${P}.tar.gz"
-
-LICENSE="GPL-3"
-SLOT="0"
-KEYWORDS="amd64 ~arm ~arm64 sparc x86"
-IUSE="curl gnutls ipv6 ldap mysql dns fping game postgres radius samba 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
-# will be built only if snmpget from net-analyzer/net-snmp[-minimal] is
-# installed. End result: most of our runtime dependencies are required
-# at build time as well.
-#
-# REAL_DEPEND contains the dependencies that are actually needed to
-# build. DEPEND contains those plus the automagic dependencies.
-#
-REAL_DEPEND="dev-lang/perl
-	curl? (
-		dev-libs/uriparser
-		net-misc/curl
-	)
-	ldap? ( net-nds/openldap:= )
-	mysql? ( || ( dev-db/mysql-connector-c dev-db/mariadb-connector-c ) )
-	postgres? ( dev-db/postgresql:= )
-	ssl? (
-		!gnutls? (
-			dev-libs/openssl:0=
-		)
-		gnutls? ( net-libs/gnutls )
-	)
-	radius? ( net-dialup/freeradius-client )"
-
-DEPEND="${REAL_DEPEND}
-	dns? ( net-dns/bind-tools )
-	game? ( games-util/qstat )
-	fping? ( net-analyzer/fping )
-	samba? ( net-fs/samba )
-	ssh? ( virtual/openssh )
-	snmp? ( dev-perl/Net-SNMP
-			net-analyzer/net-snmp[-minimal] )"
-
-# Basically everything collides with nagios-plugins.
-RDEPEND="${DEPEND}
-	acct-group/nagios
-	acct-user/nagios
-	!net-analyzer/nagios-plugins"
-
-# At least one test is interactive.
-RESTRICT="test"
-
-PATCHES=(
-	"${FILESDIR}/${PN}-gnutls.patch" #880211
-	"${FILESDIR}/${PN}-fix-check-http-segfault.patch" #893252
-)
-
-src_configure() {
-	append-flags -fno-strict-aliasing
-
-	# Use an array to prevent econf from mangling the ping args.
-	local myconf=()
-
-	if use ssl; then
-		myconf+=( $(use_with !gnutls openssl /usr)
-				  $(use_with gnutls gnutls /usr) )
-	else
-		myconf+=( --without-openssl )
-		myconf+=( --without-gnutls )
-	fi
-
-	# The autodetection for these two commands can hang if localhost is
-	# down or ICMP traffic is filtered (bug #468296). But also the path
-	# likes to move around on us (bug #883729).
-	myconf+=( --with-ping-command="$(command -v ping) -4 -n -U -w %d -c %d %s" )
-
-	if use ipv6; then
-		myconf+=( --with-ping6-command="$(command -v ping) -6 -n -U -w %d -c %d %s" )
-	fi
-
-	econf \
-		$(use_with curl libcurl) \
-		$(use_with curl uriparser) \
-		$(use_with mysql) \
-		$(use_with ipv6) \
-		$(use_with ldap) \
-		$(use_with postgres pgsql /usr) \
-		$(use_with radius) \
-		"${myconf[@]}" \
-		--libexecdir="/usr/$(get_libdir)/nagios/plugins" \
-		--sysconfdir="/etc/nagios"
-}
-
-DOCS=( ACKNOWLEDGEMENTS AUTHORS CODING ChangeLog FAQ \
-		NEWS README REQUIREMENTS SUPPORT THANKS )
-
-pkg_postinst() {
-	elog "This ebuild has a number of USE flags that determine what you"
-	elog "are able to monitor. Depending on what you want to monitor, some"
-	elog "or all of these USE flags need to be set."
-	elog
-	elog "The plugins are installed in ${EROOT}/usr/$(get_libdir)/nagios/plugins"
-}


             reply	other threads:[~2024-06-26 11:37 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 11:36 Michael Orlitzky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-14 22:55 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/monitoring-plugins/ Michael Orlitzky
2024-11-14 19:04 Sam James
2024-11-14 19:04 Sam James
2024-11-14 19:04 Sam James
2024-09-28 12:03 Michael Orlitzky
2024-08-01 12:25 Michael Orlitzky
2024-07-01  1:37 Michael Orlitzky
2024-06-26 11:36 Michael Orlitzky
2023-12-01  3:30 Sam James
2023-11-23 19:53 Sam James
2023-11-23 16:34 Michał Górny
2023-10-23 21:34 Michael Orlitzky
2023-10-23 21:34 Michael Orlitzky
2023-05-11 20:03 Sam James
2023-04-17 11:56 Sam James
2023-04-17 11:56 Sam James
2023-04-17 11:56 Sam James
2023-02-14  8:17 Sam James
2023-02-14  3:21 Sam James
2023-01-31 12:55 Sam James
2023-01-28  9:06 Sam James
2023-01-28  8:54 Sam James
2023-01-28  8:54 Sam James
2022-12-01  1:00 Michael Orlitzky
2022-12-01  1:00 Michael Orlitzky
2022-11-06 13:56 Michael Orlitzky
2022-05-03 18:09 Arthur Zamarin
2022-04-29 19:18 Sam James
2022-04-29 19:18 Sam James
2022-03-23  0:45 Sam James
2021-07-15 22:12 Conrad Kostecki
2021-07-15 21:42 Sam James
2021-07-15 21:39 Sam James
2021-07-15 21:33 Sam James
2021-05-10 13:21 Michael Orlitzky
2021-05-01 10:02 Mikle Kolyada
2021-04-03 19:53 Sam James
2021-02-04 22:27 Thomas Deutschmann
2020-11-27  7:57 Agostino Sarubbo
2020-11-27  6:36 Joonas Niilola
2020-11-27  6:36 Joonas Niilola
2020-04-17 16:24 Sergei Trofimovich
2019-03-03  0:53 Louis Sautier
2018-11-17 20:45 Sergei Trofimovich
2018-11-17 14:14 Mikle Kolyada
2018-11-15 15:48 Thomas Deutschmann
2018-09-28 18:14 Mikle Kolyada
2018-06-18 22:00 Michael Orlitzky
2018-05-08 21:16 Sergei Trofimovich
2018-05-04 15:36 Thomas Deutschmann
2018-05-04 10:52 Agostino Sarubbo
2018-02-11 11:02 Michał Górny
2017-10-22 19:59 Michael Orlitzky
2017-10-18 13:25 Sergei Trofimovich
2017-06-30  6:02 Alexis Ballier
2017-01-29 13:55 Agostino Sarubbo
2016-12-23 18:51 Michael Orlitzky
2016-08-09  4:11 Michael Orlitzky
2016-03-17 19:31 Matt Thode
2015-11-11  9:12 Agostino Sarubbo
2015-11-09 10:31 Agostino Sarubbo
2015-10-19 15:33 Ian Delaney

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=1719400862.f80b374043945c811c758e13516f1c9f98f1fe3f.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