Bug#290826: postfix: Upgrade from Postfix 2.1.4-5 to 2.1.5-4 fails

[Steve Langasek]

From the postfix postinst script:

  if [ -n "$NEWALIASES" ]; then
      echo "Running newaliases"
      rm -f /etc/aliases.db       # handle the roll to db2.0
      # newaliases chokes if hostname not set
      if [ -z "$(postconf -h myhostname||true)" ]; then
         cp -a main.cf main.cf.dpkg.$$
         postconf -e 'myhostname=debian'
         newaliases
         mv main.cf.dpkg.$$ main.cf
      else
         newaliases
      fi
  fi

The /etc/aliases.db file is *supposed* to be deleted during the upgrade.
The only way that I can reproduce this error is by setting

  alias_database = hash:/etc/aliases.db

in /etc/postfix/main.cf -- and that would be broken, because the .db
extension is not supposed to be included in the name of hash maps in
postfix.  Can you confirm the value of "postconf alias_database" on your
system?

If you do indeed have postfix configured in the above manner, I don't think
this is an RC bug, and possibly not a bug at all -- /etc/aliases is the
canonical location for the plaintext aliases file in Debian, and as a result
/etc/aliases.db is the semi-canonical location for a Berkeley db version of
this file; and /etc/aliases.db.db doesn't seem like a particularly desirable
filename in any case.

Cheers,
-- 
Steve Langasek
postmodern programmer

signature.asc
Description: Digital signature