[Pkg-sysvinit-devel] Bug#806438: Bug#806438: update-rc.d: Do not fail when initscripts is not installed

[Felipe Sateler]

Hi all,

On 2 December 2015 at 11:51, Michael Biebl <biebl at debian.org> wrote:
> On Fri, 27 Nov 2015 23:59:12 +0100 Petter Reinholdtsen <pere at hungry.com>
> wrote:
>
>> I would like to ensure the package maintainer and all the package users
>> detect incorrect boot script dependencies as early as possible,
>> preferably before the package is uploaded or at least as soon as it is
>> unloaded to unstable.
>
> I think this is a reasonable request, simply so the existing sysv init
> script don't start to bit rot.
>
> That said, the current approach to let it fail during installation only
> tests this to a very limited degree. After all, the package maintainer
> usually only has a very small subset of the Debian archive installed
> (and that's true for most of our users as well)
>
> Wouldn't it be much better, if we had some automated archive wide
> testing for this, say on ci.debian.net, where you could test arbitrary
> package combinations and where it would be simple to run insserv in
> enforcing mode?

This is a good idea.

I think there should be two categories of tests: with as little
packages as possible, and with as many packages as possible. This way
both missing dependencies and conflicts are detected.

For the first case (which is the bigger worry for passing -f), maybe
it is sufficient to run (for each init-providing package) piuparts
with sysvinit installed, as that would trigger missing dependencies.

> Outputting some warnings in big fat letters in -f mode, as Felipe
> suggested, seems like a sensible thing to do. If the package maintainer
> installs the package before uploading (which he should usually do) he
> would be able to catch the error.

Petter, would you be willing to accept such a patch so that we can
start moving forward?


-- 

Saludos,
Felipe Sateler