I would still rather removed Berkeley DB from Debian than rely on a single maintainer who seems to be knowledgeable in the databases, but still they are j
Ondrej -- Ondřej Surý (He/Him) [email protected] A gentle nudge is always appreciated if I take a little longer to reply. > On 17. 6. 2026, at 22:49, Daniel Markstedt <[email protected]> wrote: > > in an interesting turn of events, libdb is seeing serious development > activity now under a new upstream maintainer > > there is also a new bugfix release v5.3.29 from April 23 > > https://github.com/berkeleydb/libdb/releases/tag/v5.3.29 > > the new maintainer has made this statement in the project readme: > > This repository is two things at once: > > 1. A historical archive of Berkeley DB — the complete published lineage of > releases and official patches that could be recovered, preserved as tags and > GitHub Releases for reference and git diff-able history. > 2. A living fork under active development on the master branch, where new > work (bug fixes, portability, performance, and new features) happens. > > <publickey - Daniel Markstedt - 0x3C47642E.asc>
