Package: chrony Version: 3.2-2 Hi, I recently took a spike of activity on Chrony in Ubuntu with some testing and checking older bugs on it. There are Ubuntu only changes (like custom time servers), but some might qualify to be considered for Debian as well. So I wanted to open bugs for each of them to be discussed. We currently have a merge proposal up for Ubuntu at [1], and I'll link the fixes that are currently in review for you directly per-topic.
In case we modify the fixes due tot he review I'll keep you updated. </header> Description: Conversions of old $network behavior should be on online target [2]. And I think for chrony it makes sense to start when it really is online to not rely too much on the hooks to set it online. In the sense of [2] it is "client software that cannot operate without network" as it need to sync time from/to somewhere. Ubuntu-Bug: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1746458 Fix-in-Review: https://git.launchpad.net/~paelzer/ubuntu/+source/chrony/commit/?id=2baea8e0bde5d6a1de60098019fb658a4a94d489 [1]: https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/336844 [2]: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ -- Christian Ehrhardt Software Engineer, Ubuntu Server Canonical Ltd
