tag 383425 + wontfix thanks On Sat, Mar 10, 2007 at 07:40:18PM +1100, William Grant wrote: > We've had this reported[1] in Ubuntu too. It can cause upgrades to fail > if you have multiple HTTP servers installed, and opt to replace > lighttpd's configuration file. > > [1] https://bugs.launchpad.net/ubuntu/+source/lighttpd/+bug/86882
that's life ... like steve explains just under, you can't install a server along another that listens on the same port without having fixed one or another configuration file. We have two choices, either have the server work out from the box for those who only install lighttpd, and/or disable it because of the maybe 1% of people that install both lighttpd and another *httpd along it. Well, it's not really a tough choice is it ? :) On Thu, Aug 17, 2006 at 01:52:43PM -0700, Steve Langasek wrote: > And, how is this different from the behavior of any other webserver? It's > perfectly normal for a server package to start its daemon at install time > and leave the package in an unconfigured state if this fails. Surely you > can fix this by editing the config file for the package to change the port, > and then run dpkg --configure? > > In any case, this is not a grave bug, it does not render the package > unusable or mostly so. -- ·O· Pierre Habouzit ··O [EMAIL PROTECTED] OOO http://www.madism.org
pgpWul2R5rVwW.pgp
Description: PGP signature
