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

Bug#394462: marked as done (apache2: Obsolete 000-default symlink not removed on upgrade)

Your message dated Wed, 6 Jun 2007 21:03:08 +0200
with message-id <200706062103.09218.sf@sfritsch.de>
and subject line apache2: Obsolete 000-default symlink not removed on upgrade
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: apache2
Version: 2.2.3-2
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Having upgraded to Apache 2.2, I was left with two symlinks left in
/etc/apache2/sites-enabled:

 lrwxrwxrwx 1 root root 36 2006-10-21 12:51 000-default -> /etc/apache2/sites-available/default
 lrwxrwxrwx 1 root root 36 2006-02-08 21:23 default -> /etc/apache2/sites-available/default

Running 'a2dissite default' left me with the 000-default symlink, so it
appears that the name of the symlink for the default site is no longer
special-cased to start with '000-'. If this is the case, then the old
symlink is cruft and should be removed when upgrading to Apache 2.2.

- -- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (530, 'testing'), (520, 'unstable'), (510, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-k7
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages apache2 depends on:
ii  apache2-mpm-worker            2.2.3-2    High speed threaded model for Apac

apache2 recommends no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFOg7dshl/216gEHgRAp2hAJ4svul/HM5+ZiZi+8aMjC6TUVqqswCg0CEQ
AHW3EE4L867W+e8LVhmZwQA=
=HJW6
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Version: 2.2.3-4

As far as I can tell, this bug has been fixed by this change in 
2.2.3-4:

  * Refactor apache2.2-common.postinst slightly, to account for sarge
    upgrades (since it's a new package name, rather than an upgrade).
    (Closes: #396782, #415775)

--- End Message ---
Reply to: