So, this error occurs when attempting to rehabilitate systemd-timesyncd when
uninstalling/purging chrony (see restore_timesyncd() in d/postrm). This used
to be possible when systemd-timesyncd and chrony were co-installable but since
systemd 245.4-2{,ubuntu1}, this is no longer the case because systemd-timesyncd
is now a standalone package conflicting with chrony, hence the exit status 1.
To fix this, the restore_timesyncd() function found in the chrony
3.2-4ubuntu4.2 postrm script should be updated as follows:
restore_timesyncd() {
# on next reboot it would start, but that would leave time
# unsynchronized until then. So as the Conflicts in the service file
# kill systemd-timesyncd re-establish it if it is enabled
if [ -d /run/systemd/system ]; then deb-systemd-invoke start systemd-timesyncd || true
fi
From what I can see, the chrony version found in Disco Dingo is also be affected by this issue.
Hello Mark,
Debian chrony maintainer here.
So, this error occurs when attempting to rehabilitate systemd-timesyncd when purging chrony (see restore_timesyncd() in d/postrm). This used
uninstalling/
to be possible when systemd-timesyncd and chrony were co-installable but since
systemd 245.4-2{,ubuntu1}, this is no longer the case because systemd-timesyncd
is now a standalone package conflicting with chrony, hence the exit status 1.
To fix this, the restore_timesyncd() function found in the chrony
3.2-4ubuntu4.2 postrm script should be updated as follows:
restore_timesyncd() {
deb-systemd- invoke start systemd-timesyncd || true
# on next reboot it would start, but that would leave time
# unsynchronized until then. So as the Conflicts in the service file
# kill systemd-timesyncd re-establish it if it is enabled
if [ -d /run/systemd/system ]; then
fi
From what I can see, the chrony version found in Disco Dingo is also be affected by this issue.
Cheers,
Vincent