On Tue, May 13, 2014 at 05:28:10AM -0000, Martin Pitt wrote:
> thanks for the explanations!
> Steve Langasek [2014-05-12 16:09 -0000]:
> > 2. The masking support is done via startpar + startpar-upstart-bridge,
> > which is only available once we're insserv enabled.
> Ah, good to know. So startpar knows about upstart jobs and won't
> create static runlevel symlinks?
insserv still creates the links. Startpar, which is the component that runs
as boot, recognizes that the init scripts should be masked by upstart jobs.
> Because /etc/init/rc.conf doesn't seem to have any particular magic for
> ignoring rc?.d/ links which have a corresponding upstart job.
Correct.
> > 1) fix all per-package deltas in Ubuntu that removed initscripts from the
> > package in favor of upstart jobs (i.e.: bring the packages in line with
> > current Debian policy wrt upstart jobs)
Or to ensure the package is including /lib/lsb/init-functions and is used
with upstart >= 1.12.1-0ubuntu6, which includes Dimitri's change to make all
LSB init scripts DTRT automatically.
> > 2) undo the insserv/sysvinit/startpar changes that have disabled insserv in
> > Ubuntu
> > 4) drop the debhelper change
> Just to ensure that I understood this: For 1) we just put back the
> init.d scripts but *without* rc?.d/ links, i. e. we build all those
> packages with the current dh_installinit which does the "does this
> have an upstart job?" test.
Correct.
> Otherwise we'd create a dependency loop between 1) and 2) as we would then
> actually run these init.d scripts. Then we do 2) and for 4) we rebuild
> all these packages again with the "new" dh_installinit so that these
> packages do get rc?.d symlinks.
Yes, exactly.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>
On Tue, May 13, 2014 at 05:28:10AM -0000, Martin Pitt wrote:
> thanks for the explanations!
> Steve Langasek [2014-05-12 16:09 -0000]: upstart- bridge,
> > 2. The masking support is done via startpar + startpar-
> > which is only available once we're insserv enabled.
> Ah, good to know. So startpar knows about upstart jobs and won't
> create static runlevel symlinks?
insserv still creates the links. Startpar, which is the component that runs
as boot, recognizes that the init scripts should be masked by upstart jobs.
> Because /etc/init/rc.conf doesn't seem to have any particular magic for
> ignoring rc?.d/ links which have a corresponding upstart job.
Correct.
> > 1) fix all per-package deltas in Ubuntu that removed initscripts from the
> > package in favor of upstart jobs (i.e.: bring the packages in line with
> > current Debian policy wrt upstart jobs)
> That's https:/ /www.debian. org/doc/ debian- policy/ ch-opersys. html#s- upstart
> , right? I.e. we'll also need to update the init.d scripts in these
> packages to add init_is_upstart().
Or to ensure the package is including /lib/lsb/ init-functions and is used
with upstart >= 1.12.1-0ubuntu6, which includes Dimitri's change to make all
LSB init scripts DTRT automatically.
> > 2) undo the insserv/ sysvinit/ startpar changes that have disabled insserv in
> > Ubuntu
> > 4) drop the debhelper change
> Just to ensure that I understood this: For 1) we just put back the
> init.d scripts but *without* rc?.d/ links, i. e. we build all those
> packages with the current dh_installinit which does the "does this
> have an upstart job?" test.
Correct.
> Otherwise we'd create a dependency loop between 1) and 2) as we would then
> actually run these init.d scripts. Then we do 2) and for 4) we rebuild
> all these packages again with the "new" dh_installinit so that these
> packages do get rc?.d symlinks.
Yes, exactly.
-- www.debian. org/
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://
<email address hidden> <email address hidden>