Thomas Schoepf skrev:
Then don't purge it before installing apache2.2. apache2.2-common works around this.How does it do that?
It does rm -f /var/lib/dpkg/info/apache2-common.postrm in its preinst.
As this seems to be an user error rather than an error in the package, there's nothing we can do to fix this. Mind if I close the bug?Yes, I do mind. At least if you insist that it was my fault. Because then I'll insist that I rely on a package not to delete files that clearly weren't created by the package itself.
Oh, but they were created by apache2-common. You purged the package, which means that you want to erase all traces of it. When you at the same time installed another package providing the same files, you are (from the package management point of view) inconsistent and stuff breaks.
Otherwise I don't see much point in changing a package that doesn't exist anymore.
Oh, it can't be changed anywhere it matters anyway. - tfheen