Package: bdii4 Version: 4.0.2-1 Severity: serious Tags: patch User: initscripts-ng-de...@lists.alioth.debian.org Usertags: incorrect-dependency incorrect-runlevels
With dependency based boot sequencing, I discovered what I believe is a bug in the init.d scripts of this package. The bdii4 script fail to list runlevel 2 as a start runlevel, which will make the script fail to start by default in the normal Debian setup. The package description and dependency make me suspect the script should start after slapd during boot, so I propose to add that as an optional dependency to ensure this. I'm setting severity to seriuos, as the error will hit everyone installing bdii4 with the new boot ordering system. Modifying debian/patches/bdii.patch to insert this header should solve it (not doing this here, as the patch of a patch became completely unreadable): ### BEGIN INIT INFO # Provides: bdii4 # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # Should-Start: slapd # Should-Stop: slapd # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: BDII # Description: Berkeley Database Information Index ### END INIT INFO In addition this postinst is needed to detect and fix systems hit by this problem. diff -urN ../bdii4-4.0.2-2/debian/postinst ../bdii4-4.0.2-2-pere/debian/postinst --- ../bdii4-4.0.2-2/debian/postinst 1970-01-01 01:00:00.000000000 +0100 +++ ../bdii4-4.0.2-2-pere/debian/postinst 2009-09-27 16:21:23.000000000 +0200 @@ -0,0 +1,12 @@ +#!/bin/sh + +set -e + +# Recover from incorrect init.d script headers in version 4.0.2-2-5 and earlier +if [ "$1" = "configure" ] && dpkg --compare-versions "$2" le "4.0.2-2-5" \ + && [ -f /etc/rc3.d/S[0-9][0-9]bdii4 ] \ + && ! [ -f /etc/rc2.d/S[0-9][0-9]bdii4 ] ; then + update-rc.d -f bdii4 remove +fi + +#DEBHELPER# Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
