From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] fping: Update to version 5.4
Date: Tue, 26 Aug 2025 20:48:52 +0200 [thread overview]
Message-ID: <20250826184904.6229-11-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20250826184904.6229-1-adolf.belka@ipfire.org>
- Update from version 5.3 to 5.4
- Update of rootfile not required
- Changelog
5.4
Bugfixes
- Memory allocation safety checks for event storage (thanks David.A for bug report)
- Fix off-by-one boundary check in seqmap code (thanks David.A for bug report)
- The minimum value for the period (-p flag) is now 0.001 milliseconds,
since it probably never makes sense to use a smaller value, and to avoid doing
a very large memory allocation for event storage.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
lfs/fping | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lfs/fping b/lfs/fping
index 714372710..1f8d41772 100644
--- a/lfs/fping
+++ b/lfs/fping
@@ -26,7 +26,7 @@ include Config
SUMMARY = A program to ping multiple hosts
-VER = 5.3
+VER = 5.4
THISAPP = fping-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -34,7 +34,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = fping
-PAK_VER = 9
+PAK_VER = 10
DEPS =
@@ -48,7 +48,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = cc7b8bd2c8099c8bfb5e14d5b27f45cf1dc1aef24f941f5bf9c7aede95dac9472d2fe4033e8b7ea66fea8d901b99a7c908e7beff5484c0577c3f88517ef1a7ea
+$(DL_FILE)_BLAKE2 = b3c2f3ac8cb2d27593ad7a937c2fb27ab67bef3cd0d912a2a08b52bf9a96b2e5a5637567f0ef1203f86fefc99036a78ee05d69f175bdb1c2d62b6eaf6e474284
install : $(TARGET)
--
2.51.0
next prev parent reply other threads:[~2025-08-26 18:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 18:48 [PATCH] btrfs-progs: Update to version 6.16 Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship btrfs-progs Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship gdbm Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship harfbuzz Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship hwdata Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship libinih Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship lsof Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship nano Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship sudo Adolf Belka
2025-08-26 18:48 ` [PATCH] core198: Ship whois Adolf Belka
2025-08-26 18:48 ` Adolf Belka [this message]
2025-08-26 18:48 ` [PATCH] gdbm: Update to version 1.26 Adolf Belka
2025-08-26 18:48 ` [PATCH] git: Update to version 2.51.0 Adolf Belka
2025-08-26 18:48 ` [PATCH] harfbuzz: Update to version 11.4.3 Adolf Belka
2025-08-26 18:48 ` [PATCH] hwdata: Update to version 0.398 Adolf Belka
2025-08-26 18:48 ` [PATCH] libinih: Update to version 61 Adolf Belka
2025-08-26 18:48 ` [PATCH] lsof: Update to version 4.99.5 Adolf Belka
2025-08-26 18:48 ` [PATCH] nano: Update to version 8.6 Adolf Belka
2025-08-26 18:49 ` [PATCH] postfix: Update to version 3.10.4 Adolf Belka
2025-08-26 18:49 ` [PATCH] rpcbind: Update to version 1.2.8 Adolf Belka
2025-08-26 18:49 ` [PATCH] sudo: Update to version 1.9.17p2 Adolf Belka
2025-08-26 18:49 ` [PATCH] whois: Update to version 5.6.4 Adolf Belka
2025-08-26 18:49 ` [PATCH] wsdd: Update to version 0.9 Adolf Belka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250826184904.6229-11-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox