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

[Petter Reinholdtsen]

[Felipe Sateler]
> Do we want to break installs when an init script is broken but the
> user is using systemd and not sysvinit? I think this is the question
> we should be asking. The patch I proposed essentially answers "no".

As long as some of the archtectures in Debian are using sysvinit, I
suspect the best answer to that question is "yes", to ensure as many
eyeballs as possible can discover, report and fix such problems early.

> That we check for mountkernfs.sh, which lives in package initscripts,
> I consider only a proxy for the real question: is this system likely
> to ever boot into sysvinit?

To me that is not really the question.  To me it is "is the package
broken, and how should it be discovered".  As long as systemd only work
on Linux, and Debian provide kFreeBSD and Hurd kernels, we should do our
best to fix bugs in the init.d scripts.  After all, incorrect init.d
script dependencies are trivial to fix, but hard to find.

> I'm afraid I don't see any other way than triggering error at the
> point where we detect this might be a problem: when initscripts is to
> be installed again.

That is one scenario, but not the one I had in mind, as I mention above.

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.

-- 
Happy hacking
Petter Reinholdtsen