info-gnu
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gdbm-1.16 released [stable]


From: Sergey Poznyakoff
Subject: gdbm-1.16 released [stable]
Date: Wed, 27 Jun 2018 22:24:30 +0300

Hello,

This is to inform you that GNU dbm version 1.16 is available for
download. This version improves free space management. See below
for details.

Here are the compressed sources and a GPG detached signature[*]:
  https://ftp.gnu.org/gnu/gdbm/gdbm-1.16.tar.gz
  https://ftp.gnu.org/gnu/gdbm/gdbm-1.16.tar.gz.sig

Use a mirror for higher download bandwidth:
  https://ftpmirror.gnu.org/gdbm/gdbm-1.16.tar.gz
  https://ftpmirror.gnu.org/gdbm/gdbm-1.16.tar.gz.sig

Here are the MD5 and SHA1 checksums:

05ee82b8f9188a8228c2384f4b9f2eac  gdbm-1.16.tar.gz
925fbb72ea2cb7db7a93908be59b13cfcd87bb69  gdbm-1.16.tar.gz

[*] Use a .sig file to verify that the corresponding file (without the
.sig suffix) is intact.  First, be sure to download both the .sig file
and the corresponding tarball.  Then, run a command like this:

  gpg --verify gdbm-1.16.tar.gz.sig

If that command fails because you don't have the required public key,
then run this command to import it:

  gpg --keyserver keys.gnupg.net --recv-keys 3602B07F55D0C732

and rerun the 'gpg --verify' command.

This release was bootstrapped with the following tools:
  Autoconf 2.69
  Automake 1.15
  Makeinfo 5.9.93
  Bison 2.7
  Flex 2.5.37

Noteworthy changes:

* Maintain sorting order of the available block list after coalescing

This is a long-standing bug, dated back to the time when optional
coalescing of available blocks with the newly released block was
introduced. Merging the released block with an adjacent block of
available space would clobber the sorting order of the available list.
The bug was discovered due to strict database consistency checks,
introduced in version 1.15.

* Improve block merging algorithm

New implementation of block merging algorithm correctly handles
both left and right-adjacent blocks.

Best regards,
Sergey



reply via email to

[Prev in Thread] Current Thread [Next in Thread]