On Fri, 2008-08-22 at 22:11 +0200, Michael Biebl wrote: ... > As much as I disagree with upstream, that dbus should never be restarted > (I find the argument bogus, that a dbus restart is equivalent to a > kernel live-restart), I agree with Sam, that given the current > situation, and the many breakages a dbus restart produces, we would do > our users a favor if we didn't restart dbus in lenny. > > The problem is, that the dbus package in etch uses the default > dh_installinit behaviour, meaning that dbus will be stopped by the old > prerm script. So we can't avoid a dbus restart anyway for the > etch->lenny upgrade. We can only plan ahead for a lenny->lenny+1 upgrade.
Michael, does the following fit with what you said? 1. The next release of DBus should not restart the service upon package upgrade - this is what many of the DBus client developers are calling for. 2. Any client packages that depend on DBus not restarting should bump their version number and conflict with DBus>=1.3. 3. New behaviour (ie: clean restart behaviour) can be implemented in DBus 1.3, when individual packages implement whatever API is created for clean restart then they can remove the conflict. Regards, Tyson Clugg. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
