Format: 1.8
Date: Mon, 12 Nov 2018 11:39:08 +0100
Source: chrony
Binary: chrony
Architecture: armhf
Version: 3.4-1ubuntu1
Distribution: disco-proposed
Urgency: medium
Maintainer: Launchpad Build Daemon <buildd@bos02-arm64-029.buildd>
Changed-By: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Description:
 chrony     - Versatile implementation of the Network Time Protocol
Launchpad-Bugs-Fixed: 1771994 1802886
Changes:
 chrony (3.4-1ubuntu1) disco; urgency=medium
 .
   * Merge with Debian unstable (LP: #1802886). Remaining changes:
     - d/chrony.conf: use ubuntu ntp pool and server (LP 1744664)
     - Set -x as default if unable to set time (e.g. in containers) (LP: 1589780)
       Chrony is a single service which acts as both NTP client (i.e. syncing the
       local clock) and NTP server (i.e. providing NTP services to the network),
       and that is both desired and expected in the vast majority of cases.
       But in containers syncing the local clock is usually impossible, but this
       shall not break the providing of NTP services to the network.
       To some extent this makes chrony's default config more similar to 'ntpd',
       which complained in syslog but still provided NTP server service in those
       cases.
       + debian/chrony.service: allow the service to run without CAP_SYS_TIME
       + debian/control: add new dependency libcap2-bin for capsh (usually
         installed anyway, but make them explicit to be sure).
       + debian/chrony.default: new option SYNC_IN_CONTAINER to not fall back
         (Default off).
       + debian/chronyd-starter.sh: wrapper to handle special cases in containers
         and if CAP_SYS_TIME is missing. Effectively allows to run NTP server in
         containers on a default installation and avoid failing to sync time (or
         if allowed to sync, avoid multiple containers to fight over it by
         accident).
       + debian/install: make chronyd-starter.sh available on install.
       + debian/docs, debian/README.container: provide documentation about the
         handling of this case.
     - d/postrm: re-establish systemd-timesyncd on removal (LP: 1764357)
     - Notify chrony to update sources in response to systemd-networkd
       events (LP: 1718227)
       + d/links: link dispatcher script to networkd-dispatcher events routable
         and off
       + d/control: set Recommends to networkd-dispatcher
   * Dropped Changes (upstream):
     - d/p/lp-1718227-nm-dispatcher-for-networkd.patch
     - d/p/lp-1787366-fall-back-to-urandom.patch: avoid hangs when starting
       the service on newer kernels by falling back to urandom. (LP: 1787366)
   * Added Changes:
     - d/postrm: respect policy-rc.d when restoring systemd-timesyncd
       (LP: #1771994)
Checksums-Sha1:
 983134d928629bd965b76e5d56322f9079dfdc76 471956 chrony-dbgsym_3.4-1ubuntu1_armhf.ddeb
 8ecdde142a8377edd4b28c462908f99b67701ed7 5862 chrony_3.4-1ubuntu1_armhf.buildinfo
 6f4436c4c9981d6b1e7842bb7f590ed8b1d7951a 200792 chrony_3.4-1ubuntu1_armhf.deb
Checksums-Sha256:
 54d9d5661dbc5107dc1d32757de6f4c1e6d622fb1354e1521318a234b8bfccc1 471956 chrony-dbgsym_3.4-1ubuntu1_armhf.ddeb
 e55469d0fb21e7e159057522ec6cf735bb1ed0ba8167220ca6256600b534f6f9 5862 chrony_3.4-1ubuntu1_armhf.buildinfo
 5d30abcafbf0b543bda571c28433bbb8d7561968131cb77ec4a65bd219b815cd 200792 chrony_3.4-1ubuntu1_armhf.deb
Files:
 0d8515c74ea6029f024cd1f35dbda799 471956 debug optional chrony-dbgsym_3.4-1ubuntu1_armhf.ddeb
 83e583db9088ad1a578a4fa424dd1114 5862 net optional chrony_3.4-1ubuntu1_armhf.buildinfo
 a204cb4b54d802c115a244ec41cad72f 200792 net optional chrony_3.4-1ubuntu1_armhf.deb
Original-Maintainer: Vincent Blut <vincent.debian@free.fr>