From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] gdbm: Update to version 1.25
Date: Wed, 2 Apr 2025 22:25:37 +0200 [thread overview]
Message-ID: <20250402202540.3373627-2-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20250402202540.3373627-1-adolf.belka@ipfire.org>
- Update from version 1.24 to 1.25
- Update of rootfile not required
- Changelog
1.25
New function: gdbm_open_ext
This function provides a general-purpose interface for opening and
creating GDBM files. It combines the possibilities of gdbm_open
and gdbm_fd_open and provides detailed control over database file
locking.
New gdbmtool command: collisions
The command prints the collision chains for the current bucket, or
for the buckets identified by its arguments:
collisions
Display collisions for the current bucket.
collisions N
Display collisions for bucket N.
collisions N0 N1
Display collisions for the range of buckets [N0, N1].
Pipelines in gdbmtool
The output of a gdbmtool command can be connected to the input of a
shell command using the traditional pipeline syntax.
Fix a bug in block coalescing code
Other bugfixes
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
lfs/gdbm | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lfs/gdbm b/lfs/gdbm
index c601718b1..4fd3cae7e 100644
--- a/lfs/gdbm
+++ b/lfs/gdbm
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2024 IPFire Team <info@ipfire.org> #
+# Copyright (C) 2007-2025 IPFire Team <info@ipfire.org> #
# #
# This program is free software: you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
@@ -24,7 +24,7 @@
include Config
-VER = 1.24
+VER = 1.25
THISAPP = gdbm-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 79f49adbb455c2e1b91f3450037b71165fa8de82650d6402e0e22ee1f4d278fdb0bd78100659bf416e2409b432e1f8d32ecbae523980413f7148b80ee06c9f4b
+$(DL_FILE)_BLAKE2 = 6abf5f77823dda7ebcaa775d58f7a311c8f73c7521fe223398b5cb4b4831ad177cfd87fd42f2b24ca2fc5984af7d51abcc5e509ceb6aab2746a52aecb550654b
install : $(TARGET)
--
2.49.0
next prev parent reply other threads:[~2025-04-02 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 20:25 [PATCH] ffmpeg: Update to version 7.1.1 Adolf Belka
2025-04-02 20:25 ` Adolf Belka [this message]
2025-04-02 20:25 ` [PATCH] jansson: Update to version 2.14.1 Adolf Belka
2025-04-02 20:25 ` [PATCH] kmod: Update to version 34.2 Adolf Belka
2025-04-02 20:25 ` [PATCH] libarchive: Update to version 3.7.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=20250402202540.3373627-2-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