[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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

Your message dated Wed, 27 Aug 2014 21:58:45 +0200
with message-id <1587255.78GY4C1Y8F@k>
and subject line Bug#718789: apache2: upgrade wheezy -> testing (2.4.6-2) wiped out all of my log files
has caused the Debian Bug report #718789,
regarding apache2: upgrade wheezy -> testing (2.4.6-2) wiped out all of my log files
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

718789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718789
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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."


--- End Message ---
--- Begin Message ---
version: 2.4.10-1

This should be fixed now that a transitional apache2.2-common package 
has been introduced.

--- End Message ---

Reply to: