Format: 1.8
Date: Mon, 12 Nov 2018 11:39:08 +0100
Source: chrony
Binary: chrony
Architecture: amd64
Version: 3.4-1ubuntu1
Distribution: disco-proposed
Urgency: medium
Maintainer: Launchpad Build Daemon <buildd@lgw01-amd64-053.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:
 dba68a878795cfec70c05408daca2c37976a57dd 472824 chrony-dbgsym_3.4-1ubuntu1_amd64.ddeb
 bb5060eaf3fe5e02e858cf7adf334f67795212ce 6011 chrony_3.4-1ubuntu1_amd64.buildinfo
 16ff762f9184e2790b98240ea25eb1ddb9b3dd4a 219004 chrony_3.4-1ubuntu1_amd64.deb
Checksums-Sha256:
 05575418cfa3a787bba1e5431224e152cfcd623d3f0ea905b151fe2c4c6c6943 472824 chrony-dbgsym_3.4-1ubuntu1_amd64.ddeb
 13e685d886b46cf7a4a26f992eeed29a6c735db6a6b1aa15ee59f27339cb876a 6011 chrony_3.4-1ubuntu1_amd64.buildinfo
 78c894785cb518cd723ff9f8ac2ce33d0b84ff23a7a16d9624a6b8344cc526f5 219004 chrony_3.4-1ubuntu1_amd64.deb
Files:
 c55758ec16cbc0c8fa198f4038265f06 472824 debug optional chrony-dbgsym_3.4-1ubuntu1_amd64.ddeb
 c3e56479939e69c539124f9e521b6e7c 6011 net optional chrony_3.4-1ubuntu1_amd64.buildinfo
 0463f895602e1b83c026c0f1bd06014d 219004 net optional chrony_3.4-1ubuntu1_amd64.deb
Original-Maintainer: Vincent Blut <vincent.debian@free.fr>