-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
time for a new relase? #265
Comments
Hello, I recently hit this bug on FreeBSD: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253161 so we added the patch: https://www.freshports.org/commit.php?category=net-mgmt&port=smokeping&files=yes&message_id=202102020814.1128E63N095428@repo.freebsd.org Similarly, there is this bug report on Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934170 and is fixed here: https://salsa.debian.org/debian/smokeping/-/commit/82cf41226910f690d8cc44c23238cc8c7f30e371 And, probably every other *BSD or Linux have this bug or patch in their packages. |
@O2Graphics if you could create PRs for these we can add them ... and then I'll be glad todo a release |
ah :) sorry did not check out the bugreports ... I thought you ran into other problems :) |
Haha, no, no other problem ;-) PS: thanks for SmokePing, I've been using this great tool for the past 14 or 15 years! |
Not an official release but use if you want. https://github.com/deveshmanish/SmokePing/releases/tag/v2.7.4 |
+1 for a new release so we can enjoy all new improvements and bugfixes :) |
done #289 |
Hello,
The last release of Smokeping happened just a little bit more than two years ago on december 20th 2018. Since there's been a couple fixes merged in to master since then, do you think it makes sense to produce a new release?
The text was updated successfully, but these errors were encountered: