* Merge with Debian unstable. Remaining changes:
- d/control: switch to nss instead of tomcrypt (nss is in main)
- d/chrony.conf: use ubuntu ntp pool and server (LP 1744664)
* Dropped changes (in Debian)
- d/chrony.default, d/chrony.service: support /etc/default/chrony
DAEMON_OPTS in systemd environment (LP: 1746081)
- d/chrony.service: properly start after networking (LP: 1746458)
- d/usr.sbin.chronyd: allow to create /run/chrony on demand (LP: 1746444)
* Added Changes:
- debian/usr.sbin.chronyd: ensure RTC/GPS usage isn't blocked by apparmor
(LP: #1751241, Closes: #891201)
-- Christian Ehrhardt <email address hidden> Mon, 26 Feb 2018 14:44:54 +0100
This bug was fixed in the package chrony - 3.2-4ubuntu1
---------------
chrony (3.2-4ubuntu1) bionic; urgency=medium
* Merge with Debian unstable. Remaining changes: usr.sbin. chronyd: ensure RTC/GPS usage isn't blocked by apparmor
- d/control: switch to nss instead of tomcrypt (nss is in main)
- d/chrony.conf: use ubuntu ntp pool and server (LP 1744664)
* Dropped changes (in Debian)
- d/chrony.default, d/chrony.service: support /etc/default/chrony
DAEMON_OPTS in systemd environment (LP: 1746081)
- d/chrony.service: properly start after networking (LP: 1746458)
- d/usr.sbin.chronyd: allow to create /run/chrony on demand (LP: 1746444)
* Added Changes:
- debian/
(LP: #1751241, Closes: #891201)
-- Christian Ehrhardt <email address hidden> Mon, 26 Feb 2018 14:44:54 +0100