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

Bug#719097: marked as done (apache2-bin: removes most local configuration and logs on update)

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-bin: removes most local configuration and logs on update
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
immediately.)


-- 
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-bin
Version: 2.4.6-2
Severity: important

Dear Maintainer,

upon upgrading, most of my local configuration and logs were removed!

There are two problems here, both serious ones.

First,I cannot recover the logs that were recorded from the moment of
the backup to the moment of the installation.

Second, I found myself with a nonfunctional web site which requires a
significant amount of work to be on line again.  While I understand that
this perhaps may be necessary due to the major revision upgrade, I
received no notice that I was going to put my web server offline.  This
is not what is expected upon upgrade.

Moreover, I had to recover many configuration files and symbolic links
from a backup.  This is not expected from an upgrade either.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (101, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages apache2-bin depends on:
ii  libapr1                1.4.8-1
ii  libaprutil1            1.5.2-1
ii  libaprutil1-dbd-mysql  1.5.2-1
ii  libaprutil1-ldap       1.5.2-1
ii  libc6                  2.17-7
ii  libcap2                1:2.22-1.2
ii  libldap-2.4-2          2.4.31-1+nmu2
ii  liblua5.1-0            5.1.5-4
ii  libpcre3               1:8.31-2
ii  libssl1.0.0            1.0.1e-3
ii  libxml2                2.9.1+dfsg1-2
ii  perl                   5.14.2-21
ii  zlib1g                 1:1.2.8.dfsg-1

apache2-bin recommends no packages.

Versions of packages apache2-bin suggests:
ii  apache2-doc                     2.4.6-2
ii  apache2-suexec-custom           2.4.6-2
ii  elinks [www-browser]            0.12~pre6-1
ii  epiphany-browser [www-browser]  3.4.2-2.1
ii  galeon [www-browser]            2.0.7-2.1+b1
ii  iceweasel [www-browser]         10.0.12esr-1+nmu1
ii  lynx-cur [www-browser]          2.8.8dev.12-2
ii  w3m [www-browser]               0.5.3-8

Versions of packages apache2 depends on:
ii  apache2-data  2.4.6-2
ii  lsb-base      4.1+Debian12
ii  mime-support  3.54
ii  perl          5.14.2-21
ii  procps        1:3.3.4-2

Versions of packages apache2 recommends:
ii  ssl-cert  1.0.32

Versions of packages apache2 suggests:
ii  apache2-doc                     2.4.6-2
ii  apache2-suexec-custom           2.4.6-2
ii  apache2-utils                   2.4.6-2
ii  elinks [www-browser]            0.12~pre6-1
ii  epiphany-browser [www-browser]  3.4.2-2.1
ii  galeon [www-browser]            2.0.7-2.1+b1
ii  iceweasel [www-browser]         10.0.12esr-1+nmu1
ii  lynx-cur [www-browser]          2.8.8dev.12-2
ii  w3m [www-browser]               0.5.3-8

Versions of packages apache2-bin is related to:
ii  apache2      2.4.6-2
ii  apache2-bin  2.4.6-2

-- no debconf information

--- 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: