Turns out sipb-xen-www's init script was the problem, not sipb-xen-www/3.14.1
authorEvan Broder <broder@mit.edu>
Sun, 5 Oct 2008 04:00:25 +0000 (00:00 -0400)
committerEvan Broder <broder@mit.edu>
Sun, 5 Oct 2008 04:00:25 +0000 (00:00 -0400)
apache's. Install a fix

svn path=/trunk/packages/sipb-xen-www/; revision=1047

debian/changelog
debian/rules
debian/sipb-xen-www.postinst

index 23c03ba..c86a8f7 100644 (file)
@@ -1,3 +1,9 @@
+sipb-xen-www (3.14.1) unstable; urgency=low
+
+  * Try again, now that I actually understand what the problem is
+
+ -- Evan Broder <broder@mit.edu>  Sat, 04 Oct 2008 23:58:46 -0400
+
 sipb-xen-www (3.14) unstable; urgency=low
 
   * Try to fix startup ordering problem by specifying that the new startup
index bef8ef4..1c529e4 100755 (executable)
@@ -7,5 +7,7 @@ DEB_DIVERT_FILES_sipb-xen-www += \
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/rules/config-package.mk
 
+DEB_UPDATE_RCD_PARAMS_sipb-xen-www += defaults 91 9
+
 binary-fixup/sipb-xen-www::
        svn co $$(invirt-getconf svn.uri)/trunk/packages/sipb-xen-www/code/ $(DEB_DESTDIR)/var/www/sipb-xen-www
index 5ddf6f9..7f213a0 100755 (executable)
@@ -24,6 +24,10 @@ case "$1" in
        make clean && make all
        chgrp -R sipb-xen .
        chmod -R g+w .
+        
+        # Our init script proxies all requests Apache's, so Apache's
+        # running is just a NOP
+        update-rc.d -f apache2 remove
     ;;
 
     abort-upgrade|abort-remove|abort-deconfigure)