Package: postfix-lmdb Version: 3.7.11-0+deb12u1 Severity: important X-Debbugs-Cc: carpe...@adobe.com
During upgrades of postfix-lmdb, lmdb map module is removed from /etc/postfix/dynamicmaps.cf by postfix-lmdb.prerm (delmap lmdb). This removal is taken into account immediately by postfix, and is visible in logs such as: postfix/cleanup[3005561]: warning: lmdb:/etc/postfix/vdomains is unavailable. unsupported dictionary type: lmdb It's then re-added in dynamicmaps.cf by postfix-lmdb.postinst. But this doesn't trigger a module reload, leaving Postfix in a potentially broken state. Manually removing & re-adding the line in /etc/postfix/dynamicmaps.cf also simulates the issue. To be fair, Postfix automatically unloading but not reloading the map module seems like an upstream bug. But even if reloading happened, this would leave Postfix broken during the update. Could we simply not touch dynamicmaps.cf during upgrades? Note: * if may affect other map modules (ex: postfix-cdb) * the bug look similar to: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865005 -- System Information: Debian Release: 12.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-cloud-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages postfix-lmdb depends on: ii libc6 2.36-9+deb12u7 ii liblmdb0 0.9.24-1 ii postfix 3.7.11-0+deb12u1 postfix-lmdb recommends no packages. postfix-lmdb suggests no packages. -- no debconf information
