Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 678884 - net-analyzer/smokeping-2.7.3 should depend on >=net-analyzer/fping-3.16
Summary: net-analyzer/smokeping-2.7.3 should depend on >=net-analyzer/fping-3.16
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Netmon Herd
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-27 00:50 UTC by nic
Modified: 2019-03-28 01:47 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nic 2019-02-27 00:50:57 UTC
smokeping 2.7.3 implemented changes which are incompatible with gentoo's stable fping 3.13

https://github.com/oetiker/SmokePing/commit/681457d0872057f79e2b2f97fa6ff8b6b415b48c


Upstream has since committed a workaround after smokeping-2.7.3 release to accommodate distributions still shipping older fping packages

https://github.com/oetiker/SmokePing/commit/56a054874d7974b49c7ba43e4c7510086453bce4


So we have a few options. If we want to wait until the next smokeping release number, this issue should be mitigated.

Otherwise. Please consider depending on a newer version of fping. I've tested with both 4.1 and latest 4.2 without issues.

 -       >=net-analyzer/fping-4.1[suid]
 +       >=net-analyzer/fping-2.4_beta2-r2[suid]

Thank you
Comment 1 Jeroen Roovers gentoo-dev 2019-02-27 10:57:22 UTC
(In reply to nic from comment #0)

> https://github.com/oetiker/SmokePing/commit/56a054874d7974b49c7ba43e4c7510086453bce4

"If an old binary is found when starting up our FPing probe, we'll
disable use of the new switches in order to maintain functionality to
users with older versions of fping."

Doesn't look like it's absolutely necessary.
Comment 2 nic 2019-03-28 01:47:25 UTC
> Doesn't look like it's absolutely necessary.

Unless I'm miss understanding the timeline, our 2.7.3 package is broken for that commit occurred after that point release.

Yes, I agree this will eventually be fixed in the next smokeping version release.