Format: 1.8
Date: Tue, 14 May 2019 12:49:30 +0200
Source: chrony
Binary: chrony
Architecture: amd64
Version: 3.4-4ubuntu1
Distribution: eoan-proposed
Urgency: medium
Maintainer: Launchpad Build Daemon <buildd@lgw01-amd64-031.buildd>
Changed-By: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Description:
 chrony     - Versatile implementation of the Network Time Protocol
Launchpad-Bugs-Fixed: 1828992
Changes:
 chrony (3.4-4ubuntu1) eoan; urgency=medium
 .
   * Merge with Debian unstable (LP: #1828992). Remaining changes:
     - d/chrony.conf: use ubuntu ntp pool and server (LP 1744664 1754358)
     - 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) [fixed a minor typo in the comment in this update]
       + 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 chrony-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)
     - d/postrm: respect policy-rc.d when restoring systemd-timesyncd
       (LP 1771994)
   * Added Changes:
     - removed d/init to avoid weird interactions between sysV and systemd
   * Dropped Changes:
     - 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
       [Those are in Debian, except that we agreed to have networkd-dispatcher
        to only be a Suggests]
Checksums-Sha1:
 843499ca641ed700931d376e0e590a10ea2041b8 394660 chrony-dbgsym_3.4-4ubuntu1_amd64.ddeb
 63df58470e34e6ba443bde297ba476c11736261a 6068 chrony_3.4-4ubuntu1_amd64.buildinfo
 ac2bb0c179899e04d619b3d0d20de9930e3268f8 219028 chrony_3.4-4ubuntu1_amd64.deb
Checksums-Sha256:
 d29d48552dc80bb69eec8f4a3cb5fd567db1687c6d330a68834f1467ce5848d1 394660 chrony-dbgsym_3.4-4ubuntu1_amd64.ddeb
 8dde91cafd29b66a9461805d4a955c860fbbbae3fcec7f0fffbcb74c11b10f9d 6068 chrony_3.4-4ubuntu1_amd64.buildinfo
 ae677ed56db25f4df227cf0952d12a4ebd6d47f98bf539caba04ddeef44f62f9 219028 chrony_3.4-4ubuntu1_amd64.deb
Files:
 48da2fa709e054afed7f39fc9f09ab53 394660 debug optional chrony-dbgsym_3.4-4ubuntu1_amd64.ddeb
 b12d13c795a803daade33b5e5966ad54 6068 net optional chrony_3.4-4ubuntu1_amd64.buildinfo
 19ca0a2dd36ae610686e6391e21e1f97 219028 net optional chrony_3.4-4ubuntu1_amd64.deb
Original-Maintainer: Vincent Blut <vincent.debian@free.fr>