Bug#663530: apache2.2-common: ports.conf also specifies NameVirtualHost *:80

2013-07-22 Thread Edward Welbourne
That being said please note, that NameVirtualHost itself is deprecated and not used anymore in Apache2 2.4. That's good to hear. Having to hae two things exactly in sync is always a bit weird; might as well eliminate the redundancy instead ! Eddy. -- To UNSUBSCRIBE, email to

Bug#663530: apache2.2-common: ports.conf also specifies NameVirtualHost *:80

2013-07-21 Thread Edward Welbourne
Package: apache2.2-common Version: 2.2.22-13 Followup-For: Bug #663530 Dear Maintainer, I finally decided to work out why I was getting grumbles from apache about a NameVirtualHost *:80 directive. The only configuration I've actually got enabled (i.e. symlinked from sites-enabled/ to

Bug#663530: apache2.2-common: ports.conf also specifies NameVirtualHost *:80

2013-07-21 Thread Arno Töll
Hi, On 21.07.2013 17:32, Edward Welbourne wrote: Even though I actually have a NameVirtualHost in my enabled sites-available file, matching exactly the same file's VirtualHost parameter, my configuration was broken by a NameVirtualHost *:80 elsewhere, that I knew nothing about. ... Given