The problem was likely why this happened, whether it harms, what it
means and how one can get rid of it... ;)
I've seen the same for some nvidia initscripts... and as far as I can
tell a warning is only produced when the currently set stop runlevels
differ from the ones configured in the LSB header,... but not when the
user has changed any of the start runlevels, right?
In my case I never touched these stop runlevels,.. so it was perhaps
changed by the respective maintainers.
One can get rid of it e.g. via removing the initscript and readding it
with defaults, e.g.
$ update-rc.d scriptname remove
$ update-rc.d scriptname defaults
Correct so far?
The missing LSB tags error should be obvious.
Can this bug be closed?
Regards,
Chris.
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
