On Sat, Jul 17, 2010 at 01:21:07PM +0000, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the dbus package: > > #540693: /etc/init.d/dbus: Please stop restarting services when restarting > dbus > > It has been closed by Michael Biebl <bi...@debian.org>. [...] > * debian/dbus.init > - Simplify check in start_it_up() by using the existing status action. > - Stop restarting dependent services. It was an ugly hack anyway and if > people want to restart dbus, they need take care of that themselves. > (Closes: #540693, #530395)
Thank you very much for fixing this bug. However: > * debian/dbus.postinst > - Stop restarting dbus system bus on upgrades as it breaks too many > applications and is not supported by upstream in a sensible way. > Instead trigger a reboot-required message using update-notifier. > (Closes: #530000, #573386) Ow. Please consider reverting this. Most applications seem to handle dbus restarts just fine, as long as everything attached to the bug doesn't get gratuitously restarted; the applications that don't should get fixed, and that will never happen with this change. The first of those two bugs looks like it would go away now that dbus doesn't try to restart attached services like hal (and in any case hal has nearly passed into irrelevance at this point), and the second bug has no actual explanation for why dbus had timeout issues. According to several references, the dbus API provides appropriate signals to applications that the connection has disconnected, allowing them to attempt to reconnect. Just because some upstream developers have refused to consider this case does not make it unimportant, and dbus itself has the facilities to handle it, which correct applications do successfully use. Please revert this change. Thank you, Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
