This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more a
Yep, figures that you can sync 'em up either way, with the ports or
without. It just seems kinda buggy in that it breaks what was
previously working to allow the -potential- for ssl virtual hosts.
Seems like at least a simple change to documentation in the new
ports.conf file along the lines of th
Hi Glassbox,
The correct fix is to change all of your "" to
"". Please see /usr/share/doc/apache2/NEWS.Debian.gz
for more information.
Thanks,
Ryan
--
[Intrepid Alpha 5 through Live release] NameVirtualHost entry in ports.conf
causes "NameVirtualHost *:80 has no VirtualHosts" warning and break
