Package: apache2 Version: 2.4.6-2 Severity: serious Justification: causes data loss
I discovered that on upgrading from wheezy to the current testing, which has just had 2.4.6-2 migrating to it, the entire contents of /var/log/apache2 were blitzed. I'm guessing that what I did was to purge apache2.2-common, not realising the effects of this. Although there is the protection in it about not purging if upgrading to 2.4, it seems that somehow the timings didn't work out correctly and the purge took place anyway. There's no "simple" or "obvious" solution to this, I guess, except to provide a transitional apache2.2-common package with apache2 which doesn't purge the log files on purge, now that this task has been taken over by a different package. The description would presumably say: "This package may be purged after apache2 version 2.4.6 or higher has been installed; purging prior to this may result in the loss of historical log files." Julian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
