I have been using pnp4nagios with Nagios 4.x for quite some time now, close a year. It is really annoying to have to constantly edit pnp4nagios ebuild to remove the blocker on nagios-core-4. It does not work if you use npcdmod.o, but most should use bulk mode as it is more efficient and scales better. Bulk mode works just fine, and thus no need for a blocker due to one issue when an alternative exists. https://docs.pnp4nagios.org/pnp-0.6/config#bulk_mode_with_npcd I did run into some issues, but that was with the documentation not nagios or pnp4nagios. I tried to get the document address, but pnp4nagios upstream is unfriendly and wanted to play the blame game. Blaming nagios for a pnp4nagios issue. https://github.com/lingej/pnp4nagios/issues/121 Please consider removing this blocker. I rather not have to maintain a copy of said package just to avoid a blocker. Yes I know I can switch to incinga, and I might eventually. For now just would like to get the blocker removed. Thank you!
+1
I'm going to do this in the next day or so, along with a version bump and a ton of other fixes. Speak now or forever hold your peace =)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8a6c86311831919c79c94f0b4744e05691fe5045 commit 8a6c86311831919c79c94f0b4744e05691fe5045 Author: Michael Orlitzky <mjo@gentoo.org> AuthorDate: 2017-11-02 16:33:39 +0000 Commit: Michael Orlitzky <mjo@gentoo.org> CommitDate: 2017-11-04 23:37:20 +0000 net-analyzer/pnp4nagios: new revision to fix nagios/icinga "or" dependency. Previous revisions of pnp4nagios have an "or" dependency on either Nagios or Icinga, || ( net-analyzer/nagios-core net-analyzer/icinga ... The way "or" dependencies work is that they are considered satisfied if any elements of the associated group are installed. Thus the above stanza allows Nagios and Icinga to be swapped out without rebuilding pnp4nagios. That is incorrect, since later in the ebuild, nagios- or icinga-specific paths are compiled into pnp4nagios. The usual solution to that problem is to choose a default package that satisfies the "one of these" dependency, but to allow the user to specify one with a USE flag. This new revision adds three USE flags: icinga, icinga2, and nagios. The "nagios" flag is enabled by default, and builds pnp4nagios against net-analyzer/nagios. The other flags build against the associated package. In the process, the dependency on nagios-3.x was loosened to accept nagios-4.x as well. The nagios-3.x series has been end-of-life'd, and has multiple open security bugs. Bug: https://bugs.gentoo.org/628086 Bug: https://bugs.gentoo.org/629380 Bug: https://bugs.gentoo.org/636234 Closes: https://bugs.gentoo.org/600424 Package-Manager: Portage-2.3.8, Repoman-2.3.3 net-analyzer/pnp4nagios/metadata.xml | 16 ++++++++++++++ ...s-0.6.26.ebuild => pnp4nagios-0.6.26-r1.ebuild} | 25 ++++++++++++++-------- 2 files changed, 32 insertions(+), 9 deletions(-)
