[ubuntu/focal-proposed] chrony 3.5-6ubuntu1 (Accepted)

[Christian Ehrhardt]

chrony (3.5-6ubuntu1) focal; urgency=medium

  * Merge with Debian unstable (LP: #1866753). 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.

Date: Thu, 12 Mar 2020 11:02:33 +0100
Changed-By: Christian Ehrhardt <christian.ehrhardt at canonical.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://launchpad.net/ubuntu/+source/chrony/3.5-6ubuntu1
-------------- next part --------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 12 Mar 2020 11:02:33 +0100
Source: chrony
Binary: chrony
Architecture: source
Version: 3.5-6ubuntu1
Distribution: focal
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Christian Ehrhardt <christian.ehrhardt at canonical.com>
Description:
 chrony     - Versatile implementation of the Network Time Protocol
Launchpad-Bugs-Fixed: 1866753
Changes:
 chrony (3.5-6ubuntu1) focal; urgency=medium
 .
   * Merge with Debian unstable (LP: #1866753). 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.
Checksums-Sha1:
 2e005320a976955f6a90587b3b41184eb98869f2 2424 chrony_3.5-6ubuntu1.dsc
 28caf04450b8a355d496d391c0f61ccda524ec7a 40172 chrony_3.5-6ubuntu1.debian.tar.xz
 a8e01949a1acdedb56c0fbf90f5fce9e86d643b1 6849 chrony_3.5-6ubuntu1_source.buildinfo
Checksums-Sha256:
 c5c324ad153ca018fdf4755b7e3c6cf408c7d59e66a45bb455ca483152469c2f 2424 chrony_3.5-6ubuntu1.dsc
 5a45476c1b1dc9116f01940b1c0cad376558cdb7cce196b5aa73b860f616bc33 40172 chrony_3.5-6ubuntu1.debian.tar.xz
 3064dbced259791639f592531d6b750fe0a33329d84f42b34b46c8a0cb15e8ec 6849 chrony_3.5-6ubuntu1_source.buildinfo
Files:
 6e43a695a4c27c452c1ed3c204a3cc4b 2424 net optional chrony_3.5-6ubuntu1.dsc
 0e850c3b5cec7e9df501833346178358 40172 net optional chrony_3.5-6ubuntu1.debian.tar.xz
 5247921656e1e8100c410c5f3ce9ed10 6849 net optional chrony_3.5-6ubuntu1_source.buildinfo
Original-Maintainer: Vincent Blut <vincent.debian at free.fr>

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEktYY9mjyL47YC+71uj4pM4KAskIFAl5rKXgACgkQuj4pM4KA
skKzyQ/7BH0Vv7cFFKsjWYt6qOylryCj6+8B2N1GjGmq9kNZY+rke2qyXwXR4oA8
jT9krCP0QT/HN/wtj1lXRnGDYwTvZIbABVU3AulEQkdQFUC1f03UBw8A5dRvOYZM
I9rdBMofbgjbh0mG0AiN7uuohajcTiow24pcmbE2HXxfO0UqlDzbvrKnYq2nhE6c
lcXFPKA7FiqJ96/G661LEidYJZFFnRxiSIaD1EXFHjwN3Awh8KJmIwqAL/LRkiPi
/+5sV3VucMYqr402+IU1HN8seFG9hDkkLZGhXQdyYq3lc9fqANtCOmkRULE0okO/
k0ti/8Ey1VkoYOgzYO17IESmTWzhvpiMy+lP8EMNSsKoL7vhtLKOpkpxl5DpqBXT
NwOECn98t9NibyynAgMpeFwfcfvKiWQY2+vu78sRK93glnmpgB5PPBSvr3eKUgKn
K6QqFHzc+U0caXLUASJFu8W2mLAGJyGoGK83npsls1WgBxOyDPqBPuGOlsVZIYwj
+JGuSZ6buX2JNWY2KKBoqHsuD07TPkne1l79djA8lUSfcOwv4330RkWlCJvZdRdf
D5opakoxSBiTLYUnQenwLusphvAWGouoSKqlnzxg003f4Reccf9WzXXQ93kiFSsg
oLek3hfEMVRKc+68QtrEZxjU4JfWzdJliNONvgqV7YO9kxjatB4=
=nokh
-----END PGP SIGNATURE-----