On Wed, 2009-07-15 at 14:32 +0000, Nelson Elhage wrote:
> *** This bug is a duplicate of bug 399676 ***
> https://bugs.launchpad.net/bugs/399676
>
> I don't think it is accurate to characterize this as a duplicate of bug
> #399676. While it is true that solving that bug would make it possible
> to close this bug, they are not the same issue. My claim is that, as
> long as dbus does not support stateful restarts, it is still
> unnecessarily annoying to blindly request a reboot on every upgrade.
> Instead, the init script should test for specific versions where it is
> known to be particularly important (for e.g. security reasons) that the
> user upgrade soon, and only then present an annoying reboot
> notification.
>
Which would mean that for every such release, the developer would forget
to do so.
This also wouldn't work *across* releases, e.g. if you update to a minor
release - how would you know that you actually updated across a major
release.
Scott
--
Scott James Remnant
<email address hidden>
On Wed, 2009-07-15 at 14:32 +0000, Nelson Elhage wrote:
> *** This bug is a duplicate of bug 399676 *** /bugs.launchpad .net/bugs/ 399676
> https:/
>
> I don't think it is accurate to characterize this as a duplicate of bug
> #399676. While it is true that solving that bug would make it possible
> to close this bug, they are not the same issue. My claim is that, as
> long as dbus does not support stateful restarts, it is still
> unnecessarily annoying to blindly request a reboot on every upgrade.
> Instead, the init script should test for specific versions where it is
> known to be particularly important (for e.g. security reasons) that the
> user upgrade soon, and only then present an annoying reboot
> notification.
>
Which would mean that for every such release, the developer would forget
to do so.
This also wouldn't work *across* releases, e.g. if you update to a minor
release - how would you know that you actually updated across a major
release.
Scott
--
Scott James Remnant
<email address hidden>