Hi... On Tue, Sep 30, 2003 at 10:53:13PM -0500, Steve Langasek wrote: > On Mon, Sep 29, 2003 at 10:47:09PM +0200, Matthias Klose wrote: > > > Missing builds > > > ============== > > > > * libapache2-mod-python: powerpc > > > already asked for rebuild ... no reaction. > > I could take a look at this in the next day or two, if no one else > bites.
I'm the maintainer (just returning from an extended unexpected vacation). The problem is this (from the buildd log): Build-Depends: debhelper (>> 3.0.0), debconf, python2.2-dev (>= 2.2.3), python2.3-dev, apache2, apache2-dev (>= 2.0.46-1) Checking for already installed source dependencies... debhelper: missing debconf: already installed python2.2-dev: missing python2.3-dev: missing apache2: missing apache2-dev: missing Checking for source dependency conflicts... apache2 is a virtual package provided by: apache2-mpm-worker apache2-mpm-threadpool apache2-mpm-prefork apache2-mpm-perchild Using apache2-mpm-worker (no default, using first one) ... Setting up apache2-mpm-worker (2.0.47-1) ... Starting web server: Apache2(98)Address already in use: make_sock: could not bind to address [::]:80 no listening sockets available, shutting down Unable to open logs invoke-rc.d: initscript apache2, action "start" failed. dpkg: error processing apache2-mpm-worker (--configure): subprocess post-installation script returned error exit status 1 Setting up debconf-utils (1.3.14) ... ---- So who do I need to harass to fix this? The apache2 maintainer or the powerpc buildd maintainer? Either (i) the apache2 package should fail gracefully if it can't start the apache2 server, or (ii) the buildd should be set up so that starting the daemon does not fail (isn't there a fake start-stop-daemon for this purpose?) =) Peter
