* Detected file collision(s): * * /usr/lib64/nagios/plugins/check_uptime * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * net-analyzer/nagios-plugins-2.2.1-r3:0::gentoo * /usr/lib64/nagios/plugins/check_uptime * * Package 'net-analyzer/nagios-plugins-linux-madrisan-25' NOT merged due ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_hardened-test-20190824-231545 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.2.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Rust versions: [1] rust-1.37.0 * repository timestamp: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Wed, 28 Aug 2019 00:28:13 +0000 emerge -qpvO net-analyzer/nagios-plugins-linux-madrisan [ebuild N ] net-analyzer/nagios-plugins-linux-madrisan-25 USE="-curl"
Created attachment 588416 [details] emerge-info.txt
Created attachment 588418 [details] emerge-history.txt
Created attachment 588420 [details] etc.portage.tbz2
Created attachment 588422 [details] logs.tbz2
Created attachment 588424 [details] net-analyzer:nagios-plugins-linux-madrisan-25:20190828-011846.log
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ea1c6d16cf48074a257adfeff88d15b4eec3d5e2 commit ea1c6d16cf48074a257adfeff88d15b4eec3d5e2 Author: Louis Sautier <sbraz@gentoo.org> AuthorDate: 2019-08-28 23:53:43 +0000 Commit: Louis Sautier <sbraz@gentoo.org> CommitDate: 2019-08-28 23:54:04 +0000 net-analyzer/nagios-plugins-linux-madrisan: avoid another collision Rename check_uptime to avoid a collision with net-analyzer/nagios-plugins. Closes: https://bugs.gentoo.org/693008 Package-Manager: Portage-2.3.73, Repoman-2.3.17 Signed-off-by: Louis Sautier <sbraz@gentoo.org> ...x-madrisan-25.ebuild => nagios-plugins-linux-madrisan-25-r1.ebuild} | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
*** Bug 693344 has been marked as a duplicate of this bug. ***
