Bug#934945: startpar: insserv attemps to write to /etc/.boot.* even with -p option

Jesse Smith jsmith at resonatingmedia.com
Sat Aug 17 16:08:57 BST 2019

> Folks, we have serious regression. Not sure, whether it is bug in
> startpar test suite, which invokes `insserv' with `-p', but without
> `-i', or it is regression in `insserv'.

It's sort of a fore-gression. The Startpar testsuite was set up to work
with older versions of insserv, like insserv-1.14.0. I've updated the
test script to work with insserv-1.20.0. This will be fixed in the next
version of Startpar.

This is a pretty minor change, in the Startpar "testsuite/runtests"
script change the line which reads:

$INSSERV" -p etc/init.d test


$INSSERV" -p etc/init.d -i etc/init.d test

On a related note, in the startpar build log it shows the version of
startpar being tested is located at /lib/startpar/startpar. Upstream we
use the startpar executable in the local directory to make sure we are
using the fresh copy and not the system copy. It looks like maybe
Startpar is being installed before the test is run? In which case it
works out to be the same thing.

- Jesse

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.chiark.greenend.org.uk/pipermail/debian-init-diversity/attachments/20190817/1140db46/attachment.html>

More information about the Debian-init-diversity mailing list