Source: postfix Version: 3.1.3-5 Severity: serious Reason: Upgrade fails for non-default database types
Dear Maintainers,
My main.cf contains
alias_maps = lmdb:/etc/aliases
alias_database = lmdb:/etc/aliases
Upgrading postfix to 3.1.3-5 fails as follows:
~$ sudo apt install postfix
[…]
The following packages will be upgraded:
postfix (3.1.3-4 => 3.1.3-5)
postfix-lmdb (3.1.3-4 => 3.1.3-5)
2 upgraded, 0 newly installed, 0 to remove and 32 not upgraded.
[…]
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
dpkg: dependency problems prevent configuration of postfix-lmdb:
postfix-lmdb depends on postfix (= 3.1.3-5); however:
Package postfix is not configured yet.
dpkg: error processing package postfix-lmdb (--configure):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.24-7) ...
Errors were encountered while processing:
postfix
postfix-lmdb
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.
Setting the severity to serious as this also applies to
alias_database=cdb:/etc/aliases, and I guess to all postfix-* packages
for which the prerm script removes the dynamic map during upgrade. FWIW
reinstalling (using `apt install --reinstall postfix postfix-cdb`) fails
as well.
Thanks for maintaining Postfix in Debian!
Cheers,
--
Guilhem.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.8.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages postfix depends on:
ii adduser 3.115
ii cpio 2.11+dfsg-6
ii debconf [debconf-2.0] 1.5.59
ii dpkg 1.18.15
ii init-system-helpers 1.46
ii libc6 2.24-8
ii libdb5.3 5.3.28-12
ii libicu57 57.1-5
ii libsasl2-2 2.1.27~101-g0780600+dfsg-1
ii libssl1.1 1.1.0c-2
ii lsb-base 9.20161125
ii netbase 5.3
ii postfix-sqlite 3.1.3-5
ii ssl-cert 1.0.38
Versions of packages postfix recommends:
ii python3 3.5.1-4
Versions of packages postfix suggests:
ii dovecot-core [dovecot-common] 1:2.2.26.0-4
ii libsasl2-modules 2.1.27~101-g0780600+dfsg-1
ii mutt [mail-reader] 1.7.1-5
pn postfix-cdb <none>
pn postfix-doc <none>
pn postfix-ldap <none>
pn postfix-mysql <none>
pn postfix-pcre <none>
pn postfix-pgsql <none>
pn procmail <none>
pn resolvconf <none>
ii s-nail [mail-reader] 14.8.14-3
pn sasl2-bin <none>
pn ufw <none>
signature.asc
Description: PGP signature
