net-analyzer/ndoutils src_install use default function that use install-4x src/Makefile: install: install-4x $(INSTALL) -m 774 $(INSTALL_OPTS) file2sock $(DESTDIR)$(BINDIR) $(INSTALL) -m 774 $(INSTALL_OPTS) log2ndo $(DESTDIR)$(BINDIR) $(INSTALL) -m 774 $(INSTALL_OPTS) sockdebug $(DESTDIR)$(BINDIR) This is that if net-analyzer/nagios-core-3.5.1 is installed, then broker stops to work and give the following error: Error: Could not load module '/usr/bin/ndomod.o' -> file not found Install log: >>> Install ndoutils-2.0.0 into /var/tmp/portage/net-analyzer/ndoutils-2.0.0/image/ category net-analyzer make -j4 DESTDIR=/var/tmp/portage/net-analyzer/ndoutils-2.0.0/image/ install cd ./src && make install make[1]: Entering directory '/var/tmp/portage/net-analyzer/ndoutils-2.0.0/work/ndoutils-2.0.0/src' /usr/lib/portage/python2.7/ebuild-helpers/xattr/install -c -m 775 -o nagios -g nagios -d /var/tmp/portage/net-analyzer/ndoutils-2.0.0/image//usr/bin /usr/lib/portage/python2.7/ebuild-helpers/xattr/install -c -m 755 -o nagios -g nagios ndo2db-4x /var/tmp/portage/net-analyzer/ndoutils-2.0.0/image//usr/bin/ndo 2db /usr/lib/portage/python2.7/ebuild-helpers/xattr/install -c -m 755 -o nagios -g nagios ndomod-4x.o /var/tmp/portage/net-analyzer/ndoutils-2.0.0/image//usr/bin/n domod.o /usr/lib/portage/python2.7/ebuild-helpers/xattr/install -c -m 774 -o nagios -g nagios file2sock /var/tmp/portage/net-analyzer/ndoutils-2.0.0/image//usr/bin /usr/lib/portage/python2.7/ebuild-helpers/xattr/install -c -m 774 -o nagios -g nagios log2ndo /var/tmp/portage/net-analyzer/ndoutils-2.0.0/image//usr/bin /usr/lib/portage/python2.7/ebuild-helpers/xattr/install -c -m 774 -o nagios -g nagios sockdebug /var/tmp/portage/net-analyzer/ndoutils-2.0.0/image//usr/bin Hint: NDOUtils Installation against Nagios v4.x completed. If you want to install NDOUtils for Nagios v3.x please type 'make install-3x If you want to install NDOUtils for Nagios v2.x please type 'make install-2x Next step should be the database initialization/upgrade cd into the db/ directory and either: ./installdb (for a new installation) or: ./upgradedb (for an existing one) make[1]: Leaving directory '/var/tmp/portage/net-analyzer/ndoutils-2.0.0/work/ndoutils-2.0.0/src' Here is a patch to avoid such issue. Reproducible: Always
PR proposal: https://github.com/gentoo/gentoo/pull/294
commit 91b4fda (HEAD, master) Merge: 2501cdd ff72e26 Author: Patrice Clement <monsieurp@gentoo.org> Date: Tue Nov 17 13:49:42 2015 +0000 Merge remote-tracking branch 'github/pr/294'. Fixes bug 564194. Maintainer timeout. PR looks good, has been reviewed by mgorny and has been merged by myself.
(In reply to Patrice Clement from comment #2) > commit 91b4fda (HEAD, master) > Merge: 2501cdd ff72e26 > Author: Patrice Clement <monsieurp@gentoo.org> > Date: Tue Nov 17 13:49:42 2015 +0000 > > Merge remote-tracking branch 'github/pr/294'. Fixes bug 564194. > > Maintainer timeout. PR looks good, has been reviewed by mgorny and has been > merged by myself. What is a maintainer timeout? This bug report was assigned on the 26th and it's now the 18th of the next month. Meanwhile no progress showed on the bug report.
And now we have a single ebuild (no revision bump) that automagically picks a nagios version at compile time and never looks back (not even after a nagios upgrade).
I realize I'm not the maintainer of record on ndoutils, but I am preparing a version bump for it, and I maintain nagios itself. The 3.x series of nagios has outstanding security bugs that won't be fixed, and I'm going to get rid of it ASAP. As a result, the next version of ndoutils is going to target nagios-4.x exclusively, because that's all that we'll have in the tree. I have three pull requests headed upstream for ndoutils, and once they're ACKed, I'll commit the new ndoutils ebuild.
