On Tue, 6 Dec 2016 21:02:10 +0100 Guilhem Moulin <guil...@guilhem.org> wrote: > Source: postfix > Version: 3.1.3-5 > Severity: serious > Reason: Upgrade fails for non-default database types > > > Dear Maintainers, > ... > Preconfiguring packages ... > (Reading database ... 156051 files and directories currently installed.) > Preparing to unpack .../0-postfix-lmdb_3.1.3-5_amd64.deb ... > Removing lmdb map entry from /etc/postfix/dynamicmaps.cf > Unpacking postfix-lmdb (3.1.3-5) over (3.1.3-4) ... > Preparing to unpack .../1-postfix_3.1.3-5_amd64.deb ... > Unpacking postfix (3.1.3-5) over (3.1.3-4) ... > Processing triggers for libc-bin (2.24-7) ... > Processing triggers for systemd (232-7) ... > Processing triggers for man-db (2.7.5-2) ... > Setting up postfix (3.1.3-5) ... > > Postfix configuration was not changed. If you need to make changes, edit > /etc/postfix/main.cf (and others) as needed. To view Postfix configuration > values, see postconf(1). > > After modifying main.cf, be sure to run 'service postfix reload'. > > Running newaliases > postalias: fatal: unsupported dictionary type: lmdb. Is the postfix-lmdb package installed? > dpkg: error processing package postfix (--configure): > subprocess installed post-installation script returned error exit status 1 ... > > I believe this is because postfix-lmdb.prerm removes the dynamic map during > unpacking, and doesn't re-add it before postfix.postinst calls `newaliases`. > I guess the map should only be removed upon removal (`prerm remove`), or > should be re-added by the preinst script instead.
Thanks for the report and the analysis. I'll get right on this. Scott K
