Format: 1.8
Date: Mon, 12 Nov 2018 11:39:08 +0100
Source: chrony
Binary: chrony
Architecture: i386
Version: 3.4-1ubuntu1
Distribution: disco-proposed
Urgency: medium
Maintainer: Launchpad Build Daemon <buildd@lgw01-amd64-021.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:
 e71b9628ee780c2a3ecd05ae2be9b15db44562e6 437852 chrony-dbgsym_3.4-1ubuntu1_i386.ddeb
 6276cc4e9c7341a417d55342b9f015ac2597fec9 5941 chrony_3.4-1ubuntu1_i386.buildinfo
 aba440798e92c8d72d7a8bfd7d713190ff6fd517 231572 chrony_3.4-1ubuntu1_i386.deb
Checksums-Sha256:
 b0edc743230b6242812318ca44444f8e13f68a588710cfabb96a58b082e1164c 437852 chrony-dbgsym_3.4-1ubuntu1_i386.ddeb
 c6aa420e00e38e293bfe1980e4b00a9198b4cd353543cb3f0d689e02486b6685 5941 chrony_3.4-1ubuntu1_i386.buildinfo
 f1f377c8838f8e9716fb87b90b154c7bf4661792e9f0a5a43f50eafc15a16780 231572 chrony_3.4-1ubuntu1_i386.deb
Files:
 12d6ff309f8fe9aaff75f1352c2493fa 437852 debug optional chrony-dbgsym_3.4-1ubuntu1_i386.ddeb
 c8e06036055036493c59093e1a8ee8c9 5941 net optional chrony_3.4-1ubuntu1_i386.buildinfo
 c2734ea50fbe6ce08c70056366b9d4dc 231572 net optional chrony_3.4-1ubuntu1_i386.deb
Original-Maintainer: Vincent Blut <vincent.debian@free.fr>