[Thomas Schoepf] > > Then don't purge it before installing apache2.2. apache2.2-common > > works around this. > > How does it do that? It's an evil hack. You don't want to know. > 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. "Help, I purged a package and now my configuration is gone." Seriously, that's exactly what purging a package is _supposed_ to do. It removes your configuration. If you didn't want that, you shouldn't have purged apache2-common. This is why dpkg makes a distinction between the 'remove' and 'purge' actions. It seems reasonable to purge apache2-common _after_ apache 2.2 is installed. That will work. But you apparently purged it _before_ upgrading to apache 2.2. That is not reasonable, and will not work.
Attachment:
signature.asc
Description: Digital signature