From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/ndoutils/
Date: Sat, 31 Aug 2019 21:35:37 +0000 (UTC) [thread overview]
Message-ID: <1567287296.4d68327b17f6b5058ac7112f1dd0b7dcf73c89c7.mjo@gentoo> (raw)
commit: 4d68327b17f6b5058ac7112f1dd0b7dcf73c89c7
Author: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Sat Aug 31 21:00:23 2019 +0000
Commit: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Sat Aug 31 21:34:56 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4d68327b
net-analyzer/ndoutils: sync localstatedir with nagios-core.
The latest revision of nagios-core moves its localstatedir to
/var/lib/nagios. Because ndoutils is a bit wacky, the simplest
way to keep it working is to force a rebuild of ndoutils with
the same localstatedir and PID directory.
Package-Manager: Portage-2.3.69, Repoman-2.3.16
Signed-off-by: Michael Orlitzky <mjo <AT> gentoo.org>
.../{ndoutils-2.1.3-r1.ebuild => ndoutils-2.1.3-r2.ebuild} | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/net-analyzer/ndoutils/ndoutils-2.1.3-r1.ebuild b/net-analyzer/ndoutils/ndoutils-2.1.3-r2.ebuild
similarity index 89%
rename from net-analyzer/ndoutils/ndoutils-2.1.3-r1.ebuild
rename to net-analyzer/ndoutils/ndoutils-2.1.3-r2.ebuild
index 018e14d53e3..784309fee43 100644
--- a/net-analyzer/ndoutils/ndoutils-2.1.3-r1.ebuild
+++ b/net-analyzer/ndoutils/ndoutils-2.1.3-r2.ebuild
@@ -17,7 +17,7 @@ KEYWORDS="~amd64 ~ppc ~x86"
DEPEND="dev-db/mysql-connector-c
dev-perl/DBD-mysql
dev-perl/DBI
- >=net-analyzer/nagios-core-4"
+ >=net-analyzer/nagios-core-4.4.5"
RDEPEND="${DEPEND}
virtual/mysql"
@@ -42,16 +42,16 @@ PATCHES=(
src_configure() {
# The localstatedir is where our socket will be created by the
- # nagios daemon, so we put it in /var/nagios where the "nagios" user
- # will be able to write.
+ # nagios daemon, so we put it in /var/lib/nagios where the "nagios"
+ # user will be able to write.
#
# And normally, we would use /run for the pid file, but the daemon
- # drops permissions before creating it, the the piddir also needs
+ # drops permissions before creating it, so the piddir also needs
# to be writable by the nagios user.
econf --enable-mysql \
- --localstatedir=/var/nagios \
+ --localstatedir=/var/lib/nagios \
--sysconfdir=/etc/nagios \
- --with-piddir=/var/nagios
+ --with-piddir=/var/lib/nagios
}
src_compile() {
next reply other threads:[~2019-08-31 21:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-31 21:35 Michael Orlitzky [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-06 21:25 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/ndoutils/ David Seifert
2019-03-11 4:48 Aaron Bauman
2018-09-23 1:27 Michael Orlitzky
2017-11-07 12:35 Michael Orlitzky
2015-11-18 5:06 Jeroen Roovers
2015-11-18 5:06 Jeroen Roovers
2015-11-17 13:54 Patrice Clement
2015-11-17 13:54 Patrice Clement
2015-08-12 4:36 Jeroen Roovers
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=1567287296.4d68327b17f6b5058ac7112f1dd0b7dcf73c89c7.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