[Pkg-utopia-maintainers] Bug#466503: Bug#466503: Bug#466503: dbus: Fail to remove stop scripts for runlevel 0 and 6 with file-rc and insserv

[Michael Biebl]

[Resending my initial email. The first email didn't reach the bug report
as the bug was already archived]
Michael Biebl wrote:
> Petter Reinholdtsen wrote:
>> In short, this way of updating the boot sequence do not work properly
>> in Debian.  To get it working with insserv, one would need to not use
>> hardcoded sequence numbers.  To get it working with file-rc, one would
>> need to use the features provided by update-rc.d.  As far as I know,
>> the only working way to update the start and stop sequence in Debian
>> is to remove them all and insert them again.
> 
> Hm, but how do we preserve existing user configuration then (e.g. might
> have changed the priorieties or disabled the service altogether)?
> Afaik, update-rc.d -f dbus remove will forcefully remove all existing K
> and S links.

Hi Petter,

I wanted to let you know, that I'm going to revert this change we
implemented in dbus 1.1.20-1

I used this remove/insert approach in avahi-daemon, and when I asked for
a freeze-exception, this spawned a lengthy discussion on debian-release.
The overall consesus was, that is is *not* okay, to force-fully remove
local modifications. Our RM himself as a consequence even filed a RC bug
against avahi-daemon [1].

I thus would ask you, to no longer suggest the above approach to other
maintainers and file bugs about it.

Afaics, there are two cases we have to consider:
a) Updating start/stop priorities
b) Updating list of inactive/active runlevels (this is relevant for the
latest efforts to remove kill scripts from 0,6, aka as Teardown in Ubuntu)

For a), I can't see a policy-compliant way, that would update the
priorities correctly for sysv-rc, file-rc and insserv.
So, our safest bet is to only support sysv-rc, as this is our default
init system and wait for a proper update-rc.d API.
As insserv is new in lenny, this upgrade issue with insserv affects
unstable/testing users only anyways.

But as I mentioned in earlier emails, imho insserv should handle this
case automatically, i.e. if the LSB header is updated and dependencies
are added/removed, "update-rc.d $service" should recalculate the
dependencies. It should not be necessary to remove the symlinks before.

For b), the situation is a bit different. In a bug report against hal
[2], we concluded that it is safe to do
rm -f /etc/rc[06].d/K??service
So this would work with sysv-rc and insserv, but not with file-rc.

The changes in dbus, where a combination of both.
A change to the priorities and the removal of the stop symlinks in 0,6.

So, what I intend to do, is to use
rm -f /etc/rc[06].d/K??dbus
and lool's old code to update the start/stop priorities.

If you have any concerns or objections, please let us know.

Cheers,
Michael


[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499815
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501662
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?





-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-utopia-maintainers/attachments/20081024/fc4c7158/attachment.pgp