On 06.05.2026 14:06, Vincent Lefevre wrote:
On 2026-05-05 20:42:25 +0000, Debian FTP Masters wrote:Changes: postfix (3.11.2-3) unstable; urgency=medium . * d/functions: prevent cdb & lmdb removal from dynamicmaps.cf (Closes: #1135765)I'm wondering what this is supposed to mean. Upgrading postfix from 3.11.0-4 to 3.11.2-3 has the effect to remove the following lines cdb postfix-cdb.so dict_cdb_open mkmap_cdb_open lmdb postfix-lmdb.so dict_lmdb_open mkmap_lmdb_open from the /etc/postfix/dynamicmaps.cf file.
This is exactly what this bug report (#1135765) is about, and exactly the action which 3.11.2-3 supposed to prevent. Can you please tell me how did you upgrade postfix package? If the workaround doesn't work, I definitely want to know more details.
Everything seems to be fine, but I have in the logs: May 06 12:29:27 qaa postfix/cleanup[833152]: warning: /etc/postfix/canonical: hash/btree support is deprecated. Please switch to cdb or lmdb. May 06 12:29:27 qaa postfix/cleanup[833152]: warning: See /usr/share/doc/postfix/NON_BERKELEYDB_README.gz for more info. May 06 12:29:27 qaa postfix/smtp[833156]: warning: /etc/postfix/sasl_passwd: hash/btree support is deprecated. Please switch to cdb or lmdb. May 06 12:29:27 qaa postfix/smtp[833156]: warning: See /usr/share/doc/postfix/NON_BERKELEYDB_README.gz for more info. May 06 12:29:27 qaa postfix/tlsmgr[833157]: warning: /var/lib/postfix/smtp_scache: hash/btree support is deprecated. Please switch to cdb or lmdb. May 06 12:29:27 qaa postfix/tlsmgr[833157]: warning: See /usr/share/doc/postfix/NON_BERKELEYDB_README.gz for more info.
This is unrelated.
as I haven't migrated yet (I was wondering whether dpkg-reconfigure would do a part of the migration at some point later, for things that were configured by default just after postfix installation, i.e. configuration lines that I did not add manually).
I don't have plans to let dpkg-reconfigure do this. For the lifetime of forky this warning will be shown if users aren't migrated, and after forky, support for hash/btree maps will be gone for good. You can refer to the file it mentions for more information about the way it is possible to perform migration. Thanks, /mjt
