It included support for fping6, see https://github.com/schweikert/fping/pull/139 Reproducible: Always
Created attachment 579766 [details] fping-4.2.ebuild
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d31bc9e7640adaf5b8c7c1dd3591458d06d60fd3 commit d31bc9e7640adaf5b8c7c1dd3591458d06d60fd3 Author: Jeroen Roovers <jer@gentoo.org> AuthorDate: 2019-06-17 09:26:51 +0000 Commit: Jeroen Roovers <jer@gentoo.org> CommitDate: 2019-06-17 09:27:07 +0000 net-analyzer/fping: Version 4.2 Package-Manager: Portage-2.3.67, Repoman-2.3.14 Fixes: https://bugs.gentoo.org/show_bug.cgi?id=688036 Signed-off-by: Jeroen Roovers <jer@gentoo.org> net-analyzer/fping/Manifest | 1 + net-analyzer/fping/fping-4.2.ebuild | 25 +++++++++++++++++++++++++ 2 files changed, 26 insertions(+)
Why you don't have included the IPv6 support in the ebuild? This ebuild creates a symlink because they included IPv6 support in the program and the symlink gives backwards compatibility and support of fping6 in other people's scripts created pre-4.x. For example: To run properly, LibreNMS requires the fping6 binary, and the newer builds don't have this binary, so this symlink is the proper way to make it run without any errors.
(In reply to INODE64 Sistemas from comment #3) > Why you don't have included the IPv6 support in the ebuild? Please file a new bug report.
*** Bug 708020 has been marked as a duplicate of this bug. ***
