Hey. Also found /etc/apt/apt.conf.d/01autoremove-postgresql to be an obsolete dpkg conffile...
Though AFAIU it's still used in the package, just not longer as a conffile "registered" to dpkg. I think the reason why it's leftover is, that the maintainer scripts remove: /etc/apt/apt.conf.d/01autoremove not: /etc/apt/apt.conf.d/01autoremove-postgresql /var/lib/dpkg/info# grep -i 01autoremove *postgresql* postgresql-common.list:/etc/apt/apt.conf.d/01autoremove-postgresql postgresql-common.postinst:dpkg-maintscript-helper rm_conffile /etc/apt/apt.conf.d/01autoremove 215~ postgresql-common -- "$@" postgresql-common.postrm: rm -f /etc/apt/apt.conf.d/01autoremove-postgresql postgresql-common.postrm:dpkg-maintscript-helper rm_conffile /etc/apt/apt.conf.d/01autoremove 215~ postgresql-common -- "$@" postgresql-common.preinst:dpkg-maintscript-helper rm_conffile /etc/apt/apt.conf.d/01autoremove 215~ postgresql-common -- "$@" postgresql-common.prerm:dpkg-maintscript-helper rm_conffile /etc/apt/apt.conf.d/01autoremove 215~ postgresql-common -- "$@" Of course, if you change that now,... you need to adapt the version to "the latest version of the package whose upgrade should trigger the operation"... so "215~" would be wrong. Quoting the manpage: For example, for a conffile removed in version 2.0-1 of a package, prior-version should be set to 2.0-1~. This will cause the conffile to be removed even if the user rebuilt the previous version 1.0-1 as 1.0-1local1. Or a package switching a path from a symlink (shipped in version 1.0-1) to a directory (shipped in version 2.0-1), but only performing the actual switch in the maintainer scripts in version 3.0-1, should set prior-version to 3.0-1~. Oh and things might be a bit more tricky here, because AFAIU the file is actually still used (just not as a "registered" conffile). It does seem to get re-created in the configure step, but that would of course loose any user modifications. Not really sure what should be done here... If it had user modification, I think dpkg-maintscript-helper rm_conffile would anyway leave the file over with some new extension... but that's of course not a "nice" transition. Maybe ask the dpkg people what they suggest in such situation? Thanks, Chris.