Revisions of gdbm
- libgdbm_compat4: Fix libgdbm version of Conflicts [bsc#1217727] (forwarded request 1131394 from kukuk)
gdbm 1.23 (forwarded request 951944 from AndreasStieger)
- version update to 1.22 * Fix file header validation * Fix key verification in sequential access * Fix testing with DejaGNU 1.6.3 * Fix stack overflow in print_usage * Fix a leak of avail entry on pushing a new avail block * New gdbmtool variables: errorexit, errormask, trace, timing * etc. see CHANGES - modified patches % gdbm-no-build-date.patch (refreshed)
- version update to 1.20 * New bucket cache The bucket cache support has been rewritten from scratch. The new bucket cache code provides for significant speed up of search operations. * Change mmap prereading strategy Pre-reading of the memory mapper regions, introduced in version 1.19 can be advantageous only when doing intensive look-ups on a read-only database. It degrades performance otherwise, especially if doing multiple inserts. Therefore, this version introduces a new flag to gdbm_open: GDBM_PREREAD. When given, it enables pre-reading of memory mapped regions. - modified patches % gdbm-no-build-date.patch (refreshed)
- version update to 1.19 * Pre-read the memory mapped regions on systems that support it. This speeds up operations on big databases. * gdbmtool: tagged initialization of structured data Initializers for structured data can be given in tagged form, e.g.: store somekey { status=2, id={a,u,x}, name="foo" } * Bugfixes: ** Preserve locking type during database reorganization - modified patches % gdbm-no-build-date.patch (refreshed) - deleted patches - gdbm-no-common.patch (upstreamed)
- added patches Build with -no-common, [bsc#1160872] + gdbm-no-common.patch
- update to 1.18.1: * Fix debian bug 910911: This restores backward compatibility with databases created by version 1.8 (and some later versions, with mmapped I/O disabled). - update to 1.18: * Fix directory entry validation * Fix improper use of GDBM_DEBUG macro * Fix spurious error from gdbm_dump and gdbm_export * Make sure gdbm_sync always returns a meaningful value - includes changes from 1.17: * Fix bug in gdbm_dump function, it did not clear the GDBM_ITEM_NOT_FOUND error marker, which is set upon its normal termination - changes upstreamed: * gdbm_close() and gdbm_sync() now return 0 on success. On error, they return -1 and set gdbm_errno and errno to the appropriate error codes - drop gdbm-close-and-sync-return-value.patch - update to 1.16: * Fix typo * New gdbmtool variables: coalesce and centfree * src/falloc.c (avail_lookup): Remove the start parameter. (_gdbm_put_av_elem): Rewrite the "can_merge" loop. - added gdbm-close-and-sync-return-value.patch see https://puszcza.gnu.org.ua/bugs/index.php?399 - update to 1.15: * Extensive database consistency checking * Improved error checking
- Version update to 1.14.1: * Manpage formating issues * Make gdbm_error thread-safe * Improve database reproducibility * Fix build with --enable-gdbm-export - Rebase patch gdbm-no-build-date.patch (forwarded request 611494 from scarabeus_iv)
- Update to version 1.12 * New configuration variable COMPATINCLUDEDIR - Small spec file cleanups (forwarded request 396680 from pluskalm)
1
- Add obsoletes to baselibs.conf. (forwarded request 245088 from fcrozat)
- update to 1.11: * Improved dump format. * New function: gdbm_count. * New utilities: gdbm_dump and gdbm_load. * gdbmtool
Rebase. (forwarded request 157562 from jengelh)
- buildrequire makeinfo
license update: GPL-3.0+ See the COPYING file (forwarded request 151441 from babelworx)
Displaying revisions 1 - 20 of 45