Bug#798242: systemd: Failed to execute operation: Connection timed out

Martin Pitt mpitt at debian.org
Mon Nov 30 06:32:02 GMT 2015


Hello James,

James Cameron [2015-11-30 10:40 +1100]:
> Is 228 planned for jessie, or should we temporarily repoint sources to
> stretch and try an update of systemd only?

Jessie has and will keep 215, we will only backport individual fixes
for it. I would strongly advise against a partial upgrade -- nobody
tests these combinations, and they are unmaintainable on a production
system.

> The problem system is still in the state it was left in when #798242
> was raised.  We've been unable to take the risk of a reboot; yet.  Can
> you speculate if reboot would be bad idea?

No, a reboot is probably the only thing which will reset the state
properly. The "35 not upgraded" packages should be okay, and
unconfigured systemd is ok as it only failed in the trigger. But
leaving udev unconfigured could lead to boot troubles, so maybe try a
round (or two) of "dpkg --configure -a" first?

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)




More information about the Pkg-systemd-maintainers mailing list