[Milan Zamazal]
> OK, added.

Good. :)

>     PR> The script used to start after the syslog collector with the
>     PR> legacy boot ordering, while the script dependencies do not list
>     PR> $syslog as a dependency.  
> 
> Should this be present even when Speech Dispatcher itself doesn't
> use syslog?  (I've added it for now as it probably doesn't hurt, but
> if it's useless I remove it again in the next upload.)

It depends.  For systems causing the kernel or other systems to
generate syslog messages, I believe it is best to depend on $syslog to
make it easier to debug the boot when something go wrong.  Also, it
make it easier for other packages (like watchdog) to insert themselves
before most services are started if all or most services depend on
$syslog.  Anyway, I do not really know the speech-dispatcher package,
so I can not really say which setting make most sense here.

>     PR> Last, it depend on festival, which is a facility not provided by
>     PR> any init.d scripts.
> 
> It is provided by /etc/init.d/festival from the package `festival', so
> it is retained.

For a moment, I started to wonder if if there was something wrong with
the archive wide checking I perform on the init.d scripts.  But closer
checking show that the festival do not provide an init.d script in
/etc/init.d/.  There is only an example file in the package:

  minerva:/# dpkg -L festival|grep init
  /usr/share/doc/festival/examples/festival.init
  /usr/share/festival/init.scm
  /usr/share/festival/siteinit.scm
  minerva:/# 

I guess your machine have an obsolete init.d script installed, which
the package maintainer didn't add code to remove when the init.d
script was dropped from the package.  Not a big problem, just keep the
relation in place, to make sure those copying the example into
/etc/init.d/ get the correct ordering. :)

>     PR> Any hope of having this issue fixed soon?
> 
> Just uploaded.  Thanks for the report and sorry for the delay.

Great. :)

Happy hacking,
-- 
Petter Reinholdtsen




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

Reply via email to