+++ This bug was initially created as a clone of Bug #1788186 +++

According to more restrictive libdb licence policy exists effort to remove libdb's dependencies.
cyrus-sasl package is now built with libdb requirement, this package could be build without libdb. libdb could be replaced by gdbm.

--- Additional comment from Robert Scheck on 2020-01-16 00:21:18 UTC ---

Filip, is there a specific reason that you suggest gdbm rather lmdb?

--- Additional comment from Filip Januš on 2020-01-16 12:35:52 UTC ---

There are multiple choices(see: https://www.cyrusimap.org/sasl/sasl/installation.html#requirements). But from cyrus-sasl installation guide:
"If you are using SASLdb, you will need to pick your backend. libsasl2 can use gdbm, Berkeley db, or ndbm to implement its user/password lookup. Most systems come with ndbm." 
I am not sure, if cyrus-sasl with gdbm has same functionality as with lmdb. If so then lmdb could be used.

--- Additional comment from Ben Cotton on 2020-02-11 17:35:04 UTC ---

This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

--- Additional comment from Simo Sorce on 2021-01-14 17:15:39 UTC ---

Hi Filip,
we have a proposed change to address this issue here:
https://src.fedoraproject.org/rpms/cyrus-sasl/pull-request/3

I guess one question is how/when we should introduce this change in Fedora.

As you can see we have a migration script, but there is currently no automatic migration of the Database during an RPM upgrade. We can probably add a scriplet to catch a DB in the default path, but applications that may provide a bdb database in an alternative path would have to be changed to invoke the upgrade script I guess.

So guidance on how to proceed would be nice.

--- Additional comment from Filip Januš on 2021-01-18 09:36:42 UTC ---

Hi, Simo
first of all thanks for your effort. It's great that you include also the support of conversion.

In the current state isn't possible to make one big Fedora change for all components, because some components need more time to implement other database support. Therefore I would recommend creating a change Into Fedora 35 for your component. 
If I can help in any way, I'll be happy to help.

--- Additional comment from Simo Sorce on 2021-01-19 20:02:57 UTC ---

Dmitry did most of the work, so thanks go to him.

We will plan for a F35 change once they open up.

--- Additional comment from Ben Cotton on 2021-02-09 16:23:50 UTC ---

This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.