diff options
| author | Michael Orlitzky <mjo@gentoo.org> | 2022-11-30 19:46:12 -0500 |
|---|---|---|
| committer | Michael Orlitzky <mjo@gentoo.org> | 2022-11-30 19:58:42 -0500 |
| commit | 1a5ad2e371f409ab9b41a7f7fedc766dd0fc0c2e (patch) | |
| tree | beb901c2af58f6bef9a0f4b2045f705ee2f9554b /dev-python/GitPython/GitPython-3.1.27.ebuild | |
| parent | d984b14556a58586e39f899fb99e5cde02265244 (diff) | |
| download | gentoo-1a5ad2e371f409ab9b41a7f7fedc766dd0fc0c2e.tar.gz gentoo-1a5ad2e371f409ab9b41a7f7fedc766dd0fc0c2e.tar.bz2 gentoo-1a5ad2e371f409ab9b41a7f7fedc766dd0fc0c2e.zip | |
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@gentoo.org>
Diffstat (limited to 'dev-python/GitPython/GitPython-3.1.27.ebuild')
0 files changed, 0 insertions, 0 deletions