Chrony would need in postinst to "systemctl restart systemd-timesyncd.service" (ignoring RC in any case) to make sure timesyncd picks up the newly deployed drop-in config.
Otherwise (see above) both will be running.
And for the test I think we want to drop:
Depends: @,
from d/t/control to avoid the systems daemon fighting with the tests daemon
I uploaded some preliminary fixes for that [1] to the PPA [2] to retest those.
Chrony would need in postinst to "systemctl restart systemd- timesyncd. service" (ignoring RC in any case) to make sure timesyncd picks up the newly deployed drop-in config.
Otherwise (see above) both will be running.
And for the test I think we want to drop:
Depends: @,
from d/t/control to avoid the systems daemon fighting with the tests daemon
I uploaded some preliminary fixes for that [1] to the PPA [2] to retest those.
[1]: https:/ /code.launchpad .net/~paelzer/ ubuntu/ +source/ chrony/ +git/chrony/ +ref/test- issues- focal /launchpad. net/~ci- train-ppa- service/ +archive/ ubuntu/ 4000
[2]: https:/