Bug#383425: lighttpd: foo

2006-10-11 Thread Mikhail Gusarov

And, how is this different from the behavior of any other webserver?

apache2 installs itself as disabled and asked to enable it in
/etc/defaults/apache2 (or at least it did it in the past).

-- 
Mikhail Gusarov
Senior Software Engineer
SWsoft, Inc.
JID: [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#383425: lighttpd: foo

2006-08-17 Thread Ken Bowley
Package: lighttpd
Version: 1.4.11-7
Severity: grave
Justification: renders package unusable

Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Johann Friedrich [EMAIL PROTECTED]
To: Debian Bug Tracking System [EMAIL PROTECTED]
Subject: lighttpd: Fails to install if another webserver is running
Message-ID: [EMAIL PROTECTED]
X-Mailer: reportbug 3.25
Date: Thu, 17 Aug 2006 01:19:07 -0700

Package: lighttpd
Version: 1.4.11-7
Severity: grave
Justification: renders package unusable

I wish to install lighttpd to use as a web server for a Ruby on Rails
application, but it will not be running on port 80 (already used by
Apache).  The postinst script fails on a new installation when Apache
(or another daemon) is already bound to port 80.

It is highly common to run lighttpd as a normal user on an unprivledged
port port and have Apache act as a proxy in the Ruby on Rails community.

Setting up lighttpd (1.4.11-7) ...
Starting web server: lighttpd2006-08-17 01:08:10: (network.c.300) can't
bind to port: localhost 80 Address already in use
 failed!
invoke-rc.d: initscript lighttpd, action start failed.
dpkg: error processing lighttpd (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 lighttpd
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.17-2-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages lighttpd depends on:
ii  libbz2-1.0  1.0.3-3  high-quality block-sorting file co
ii  libc6   2.3.6-19 GNU C Library: Shared libraries
ii  libldap22.1.30-13+b1 OpenLDAP libraries
ii  libpcre36.4-2Perl 5 Compatible Regular Expressi
ii  libssl0.9.8 0.9.8b-2 SSL shared libraries
ii  lsb-base3.1-14   Linux Standard Base 3.1 init scrip
ii  mime-support3.37-1   MIME files 'mime.types'  'mailcap
ii  zlib1g  1:1.2.3-13   compression library - runtime

Versions of packages lighttpd recommends:
pn  php4-cgi | php5-cgi   none (no description available)

-- no debconf information

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.17-2-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages lighttpd depends on:
ii  libbz2-1.0  1.0.3-3  high-quality block-sorting file co
ii  libc6   2.3.6-19 GNU C Library: Shared libraries
ii  libldap22.1.30-13+b1 OpenLDAP libraries
ii  libpcre36.4-2Perl 5 Compatible Regular Expressi
ii  libssl0.9.8 0.9.8b-2 SSL shared libraries
ii  lsb-base3.1-14   Linux Standard Base 3.1 init scrip
ii  mime-support3.37-1   MIME files 'mime.types'  'mailcap
ii  zlib1g  1:1.2.3-13   compression library - runtime

Versions of packages lighttpd recommends:
pn  php4-cgi | php5-cgi   none (no description available)

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#383425: lighttpd: foo

2006-08-17 Thread Steve Langasek
severity 383425 wishlist
thanks

On Thu, Aug 17, 2006 at 01:23:39AM -0700, Ken Bowley wrote:
 I wish to install lighttpd to use as a web server for a Ruby on Rails
 application, but it will not be running on port 80 (already used by
 Apache).  The postinst script fails on a new installation when Apache
 (or another daemon) is already bound to port 80.

 It is highly common to run lighttpd as a normal user on an unprivledged
 port port and have Apache act as a proxy in the Ruby on Rails community.

 Setting up lighttpd (1.4.11-7) ...
 Starting web server: lighttpd2006-08-17 01:08:10: (network.c.300) can't
 bind to port: localhost 80 Address already in use
  failed!
 invoke-rc.d: initscript lighttpd, action start failed.
 dpkg: error processing lighttpd (--configure):
  subprocess post-installation script returned error exit status 1
 Errors were encountered while processing:
  lighttpd
 E: Sub-process /usr/bin/dpkg returned an error code (1)

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.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/