<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - commit 7708588119 broke logind DBus API" href="https://bugs.freedesktop.org/show_bug.cgi?id=67131#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - commit 7708588119 broke logind DBus API" href="https://bugs.freedesktop.org/show_bug.cgi?id=67131">bug 67131</a> from <a class="email" href="mailto:michael+freedesktop@stapelberg.de" title="Michael Stapelberg <michael+freedesktop@stapelberg.de>"> Michael Stapelberg</a> <pre>(In reply to <a href="show_bug.cgi?id=67131#c1">comment #1</a>) > Note that the update 44 → 205 probably requires a reboot anyway, as the > cgroup tree changed substantially, and the old versions did not serialize > the cgroup information. Does that imply that 44 → 204 should be fine without a reboot? Also, could you please clarify what the implications are if we don’t reboot? I.e. will a systemd reexec not work for 204 → 205 (what about 44 → 205)? What stuff will break precisely? This is important for us to know since Debian does not have a good mechanism to force reboots on package upgrades.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>