Petr Baudis [2014-12-04 16:16 +0100]:
> Can't this be handled like a glibc (nss) upgrade is, using a debconf
> prompt that suggests restarting other services recursively?
In theory, anything is possible :-) However, that first assumes that
all the affected services actually support that properly;
Michael Biebl [2014-12-04 23:13 +0100]:
> I still want to upload the fix for NM in addition to that. Imho it makes
> sense to do both.
Yes, absolutely. There might be other reasons why journald restarts,
because the admin did it, or there's a crash. This sounds appropriate
and safe enough for jess
Am 04.12.2014 um 15:20 schrieb Martin Pitt:
> Michael Biebl [2014-11-27 0:17 +0100]:
>> Maybe the least invasive change is, to move the systemd-journald
>> restart into the
>> if dpkg --compare-versions "$2" lt-nl "215-3"; then
>> fi
>
> This is the typical "between rock and hard place" situation
Hi!
Can't this be handled like a glibc (nss) upgrade is, using a debconf
prompt that suggests restarting other services recursively? However,
that code in libc.postinst configure phase handling looks rather ugly
and has the services hardcoded.
Even if infeasible, it would be good to add a
Michael Biebl [2014-11-27 0:17 +0100]:
> Maybe the least invasive change is, to move the systemd-journald
> restart into the
> if dpkg --compare-versions "$2" lt-nl "215-3"; then
> fi
This is the typical "between rock and hard place" situation. I agree
that we should stop restarting it by default
Am 27.11.2014 um 00:17 schrieb Michael Biebl:
> There was a recent discussion on #systemd, where Lennart mentioned in a
> related
> context (full IRC log is attached), that restarting journald is a bad idea,
> as it is not properly supported atm:
For completeness sake, find attached the IRC log.
Package: systemd
Version: 215-6
Severity: serious
We restart systemd-journald in postinst on upgrades [0].
Unfortunately, this breaks other services like network-manager [1].
There was a recent discussion on #systemd, where Lennart mentioned in a related
context (full IRC log is attached), that r
