Martin Pitt wrote:
> This sounds like another case of
> https://github.com/systemd/systemd/issues/1505, which finally got
> fixed in version 228.
Thanks, very interesting. Yes, it sounds likely.
> ...
>
> I don't close this for now, it would be interesting to see whether
> this still happens
Martin Pitt wrote:
> James Cameron wrote:
> > 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
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
Processing control commands:
> fixed -1 228-1
Bug #798242 [systemd] systemd: Failed to execute operation: Connection timed out
Marked as fixed in versions systemd/228-1.
--
798242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798242
Debian Bug Tracking System
Contact ow...@bugs.debian.
Control: fixed -1 228-1
Hello James,
James Cameron [2015-09-07 3:19 -0500]:
> Processing triggers for systemd (215-17+deb8u1) ...
> Failed to execute operation: Connection timed out
This sounds like another case of
https://github.com/systemd/systemd/issues/1505, which finally got
fixed in
Package: systemd
Version: 215-17+deb8u1
Severity: important
Dear Maintainer,
While applying package updates (apt-get upgrade) the install of systemd or udev
failed with the following terminal output;
The following packages will be upgraded:
apache2 apache2-bin apache2-data
