Bug#718789: apache2: upgrade wheezy -> testing (2.4.6-2) wiped out all of my log files

[Julian Gilbey <jdg@debian.org>]

On Mon, Aug 05, 2013 at 04:26:41PM +0200, Arno Töll wrote:
> Yes it does, and that's expected. Read the manpage from aptitude (for
> example):
> 
>        --purge-unused
>            [..] THIS OPTION CAN CAUSE DATA LOSS! DO NOT USE IT UNLESS
> YOU KNOW WHAT YOU ARE DOING!
> 
> It's your responsibility if you use this option or apt's equivalent.
> This is the same problem as #717476. Refer there too, why an
> apache2.2-common package is problematic.
> 
> That being said we may just provide it to make these discussions finally
> (but possibly open a new can'o'worms).

True, but I had no idea that purging that unused legacy apache-2.2.x
package would mean that my modules configuration and all of my log
files would be wiped out (I had spotted the earlier problem too, but
did not realise the connection until reading the other bug report you
referred to); I would expect that if I were purging apache completely,
but not when purging legacy packages from an old version during an
upgrade.

I think enough people are likely to be stung by this one that
providing a transition apache2.2-common package would be worth doing,
with an appropriate warning in the Description field.

Thanks!

   Julian