Bug#987013: Release goal proposal: Remove Berkeley DB
- To: 987013@bugs.debian.org
- Subject: Bug#987013: Release goal proposal: Remove Berkeley DB
- From: Bastian Germann <bage@debian.org>
- Date: Sat, 14 May 2022 12:06:27 +0200
- Message-id: <[🔎] e05a0d3b-190a-7900-39c1-f016e805c561@debian.org>
- Reply-to: Bastian Germann <bage@debian.org>, 987013@bugs.debian.org
- In-reply-to: <161850313718.205852.14724994036001883500.reportbug@rockhammer.waldi.eu.org>
- References: <161850313718.205852.14724994036001883500.reportbug@rockhammer.waldi.eu.org> <161850313718.205852.14724994036001883500.reportbug@rockhammer.waldi.eu.org> <161850313718.205852.14724994036001883500.reportbug@rockhammer.waldi.eu.org>
X-Debbugs-Cc: bage@debian.org
Hi,
cyrus-sasl2 package maintainer here. I am interested in the state of this since BerkeleyDB will be removed from sasl
upstream with the next release [0]. There are several other implementations to choose from: gdbm|lmdb|ndbm. ndbm does
not exist in Debian and gdbm's GPL license would probably be problematic when combined with CMU's BSD-4-clause code.
Can someone shine a light on what a transition to lmdb would mean for cyrus-sasl2?
Can the existing databases just be used as-is or do they need a migration?
Cheers,
Bastian
[0]: https://github.com/cyrusimap/cyrus-sasl/issues/718
Reply to: