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: Thu, 1 Dec 2022 01:00:50 +0000 (UTC) [thread overview]
Message-ID: <1669856322.1a5ad2e371f409ab9b41a7f7fedc766dd0fc0c2e.mjo@gentoo> (raw)
commit: 1a5ad2e371f409ab9b41a7f7fedc766dd0fc0c2e
Author: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Thu Dec 1 00:46:12 2022 +0000
Commit: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Thu Dec 1 00:58:42 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1a5ad2e3
net-analyzer/monitoring-plugins: new revisions to fix ping path.
We pass explicit ping/ping6 commands to the monitoring-plugins
./configure script to prevent it from running those commands during the
build. However, instead of grabbing their paths from $PATH, we have
(until now) hard-coded them to /bin/ping. This has now bitten us with
net-misc/iputils-20221126.
This commit uses $(command -v ...) to get the right absolute
paths. Thanks to Daniel Pouzzner for reporting the problem and
suggesting the near-identical fix to nagios-plugins. I've made the
changes and revisions to both the ~arch and stable ebuilds to avoid as
much breakage as possible, but we will still need to coordinate the
stabilization of monitoring-plugins-2.3.2-r1 with iputils-20221126.
Closes: https://bugs.gentoo.org/883729
Signed-off-by: Michael Orlitzky <mjo <AT> gentoo.org>
...-plugins-2.3.1-r3.ebuild => monitoring-plugins-2.3.1-r4.ebuild} | 7 ++++---
...ing-plugins-2.3.2.ebuild => monitoring-plugins-2.3.2-r1.ebuild} | 7 ++++---
2 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/net-analyzer/monitoring-plugins/monitoring-plugins-2.3.1-r3.ebuild b/net-analyzer/monitoring-plugins/monitoring-plugins-2.3.1-r4.ebuild
similarity index 91%
rename from net-analyzer/monitoring-plugins/monitoring-plugins-2.3.1-r3.ebuild
rename to net-analyzer/monitoring-plugins/monitoring-plugins-2.3.1-r4.ebuild
index 70689ddedd5c..bee2b77ec739 100644
--- a/net-analyzer/monitoring-plugins/monitoring-plugins-2.3.1-r3.ebuild
+++ b/net-analyzer/monitoring-plugins/monitoring-plugins-2.3.1-r4.ebuild
@@ -76,11 +76,12 @@ src_configure() {
fi
# The autodetection for these two commands can hang if localhost is
- # down or ICMP traffic is filtered. Bug #468296.
- myconf+=( --with-ping-command="/bin/ping -4 -n -U -w %d -c %d %s" )
+ # 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="/bin/ping -6 -n -U -w %d -c %d %s" )
+ myconf+=( --with-ping6-command="$(command -v ping) -6 -n -U -w %d -c %d %s" )
fi
econf \
diff --git a/net-analyzer/monitoring-plugins/monitoring-plugins-2.3.2.ebuild b/net-analyzer/monitoring-plugins/monitoring-plugins-2.3.2-r1.ebuild
similarity index 91%
rename from net-analyzer/monitoring-plugins/monitoring-plugins-2.3.2.ebuild
rename to net-analyzer/monitoring-plugins/monitoring-plugins-2.3.2-r1.ebuild
index 68ba0969bbbc..27bd712c16c3 100644
--- a/net-analyzer/monitoring-plugins/monitoring-plugins-2.3.2.ebuild
+++ b/net-analyzer/monitoring-plugins/monitoring-plugins-2.3.2-r1.ebuild
@@ -72,11 +72,12 @@ src_configure() {
fi
# The autodetection for these two commands can hang if localhost is
- # down or ICMP traffic is filtered. Bug #468296.
- myconf+=( --with-ping-command="/bin/ping -4 -n -U -w %d -c %d %s" )
+ # 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="/bin/ping -6 -n -U -w %d -c %d %s" )
+ myconf+=( --with-ping6-command="$(command -v ping) -6 -n -U -w %d -c %d %s" )
fi
econf \
next reply other threads:[~2022-12-01 1:00 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 1:00 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
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-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=1669856322.1a5ad2e371f409ab9b41a7f7fedc766dd0fc0c2e.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