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

Christian Ehrhardt christian.ehrhardt at canonical.com
Thu Jan 23 14:10:12 UTC 2020


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

  * Merge with Debian unstable (LP: #1859969). 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.
  * Dropped changes:
    - d/t/control: destructive_system_tests only work on amd64 and s390x right
      now [fixed by backporting fixes from upstream in 3.5-5 ]
    - d/t/upstream-simulation-test-suite: ignore warnings on stderr while
      running clksim make
      [ in Debian 3.5-5 ]

chrony (3.5-5) unstable; urgency=medium

  * debian/control:
    - Bump standard-version to 4.4.1 (no change required).

  * debian/install:
    - Install 50-chrony.list in /usr/lib/systemd/ntp-units.d.

  * debian/ntp-units.d/50-chrony.list:
    - Allow timedated to interact with chronyd.

  * debian/patches/*:
    - Cherry-pick upstream commits to better manage RTCs that don't support
    interrupts. This fixes an issue exhibited when a specific upstream system
    test is run on the Ubuntu CI. Thank to Christian Ehrhardt for working
    with Miroslav Lichvar to address this problem.

  * debian/tests/control:
    - Use @builddeps@ as a test dependency for upstream_system_tests.

  [ Christian Ehrhardt ]
  * debian/tests/upstream-simulation-test-suite:
    - Redirect stderr on make call to stdout. On some architectures (e.g. armhf)
    the clksim tests compile but throw some warnings. (MR: !2)

Date: Thu, 16 Jan 2020 12:55:32 +0100
Changed-By: Christian Ehrhardt <christian.ehrhardt at canonical.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Signed-By: Andreas Hasenack <andreas at canonical.com>
https://launchpad.net/ubuntu/+source/chrony/3.5-5ubuntu1
-------------- next part --------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 16 Jan 2020 12:55:32 +0100
Source: chrony
Architecture: source
Version: 3.5-5ubuntu1
Distribution: focal
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Christian Ehrhardt <christian.ehrhardt at canonical.com>
Launchpad-Bugs-Fixed: 1859969
Changes:
 chrony (3.5-5ubuntu1) focal; urgency=medium
 .
   * Merge with Debian unstable (LP: #1859969). 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.
   * Dropped changes:
     - d/t/control: destructive_system_tests only work on amd64 and s390x right
       now [fixed by backporting fixes from upstream in 3.5-5 ]
     - d/t/upstream-simulation-test-suite: ignore warnings on stderr while
       running clksim make
       [ in Debian 3.5-5 ]
 .
 chrony (3.5-5) unstable; urgency=medium
 .
   * debian/control:
     - Bump standard-version to 4.4.1 (no change required).
 .
   * debian/install:
     - Install 50-chrony.list in /usr/lib/systemd/ntp-units.d.
 .
   * debian/ntp-units.d/50-chrony.list:
     - Allow timedated to interact with chronyd.
 .
   * debian/patches/*:
     - Cherry-pick upstream commits to better manage RTCs that don't support
     interrupts. This fixes an issue exhibited when a specific upstream system
     test is run on the Ubuntu CI. Thank to Christian Ehrhardt for working
     with Miroslav Lichvar to address this problem.
 .
   * debian/tests/control:
     - Use @builddeps@ as a test dependency for upstream_system_tests.
 .
   [ Christian Ehrhardt ]
   * debian/tests/upstream-simulation-test-suite:
     - Redirect stderr on make call to stdout. On some architectures (e.g. armhf)
     the clksim tests compile but throw some warnings. (MR: !2)
Checksums-Sha1:
 b860a41df4510bc8c2c47fc08d91ddd4847950bf 2437 chrony_3.5-5ubuntu1.dsc
 79e9aeace143550300387a99f17bff04b45673f7 458226 chrony_3.5.orig.tar.gz
 d6dee1ae5ec6f2630d112decad5b7ec0fd4a92b3 39412 chrony_3.5-5ubuntu1.debian.tar.xz
 144cca74cb427810df01950e2357326c85d6d2c0 5911 chrony_3.5-5ubuntu1_source.buildinfo
Checksums-Sha256:
 53365b812e4e557bda93557b7f36586b8edc139800d66493e79f00620a4d3825 2437 chrony_3.5-5ubuntu1.dsc
 4e02795b1260a4ec51e6ace84149036305cc9fc340e65edb9f8452aa611339b5 458226 chrony_3.5.orig.tar.gz
 f974d68d56403b3551d4effbbda1b8b4e8e97f94276ab97712273cb1d034fd88 39412 chrony_3.5-5ubuntu1.debian.tar.xz
 3752d2532959a0363e72f4d86b4b167913fda1f6a45a6e5265a4bb5093e5fd71 5911 chrony_3.5-5ubuntu1_source.buildinfo
Files:
 a06983eaa0e9e87806332b0e9e6b6c89 2437 net optional chrony_3.5-5ubuntu1.dsc
 5f66338bc940a9b51eede8f391e7bed3 458226 net optional chrony_3.5.orig.tar.gz
 7cc21dba6002546a3072604152abb107 39412 net optional chrony_3.5-5ubuntu1.debian.tar.xz
 f589fa1fbd11653ac6ce8ece219bec72 5911 net optional chrony_3.5-5ubuntu1_source.buildinfo
Original-Maintainer: Vincent Blut <vincent.debian at free.fr>

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

iQIzBAEBCgAdFiEEiGZB1jWM2kalbBxyrJg+tb9ry6kFAl4pp+EACgkQrJg+tb9r
y6lC5A//bFUkTIh0sDf2bhk+Zw/JldJkTuXqmO8RX9fK2hsm5tHDS8iNfSdrXyxp
PxwvpG/lqasyaIuKRiqkscRGNiXTEDMVTjCTPCLlG5POhBGMAjGpgG63Q2z9ToKi
Uh8QW4rOcKEMXILIHf/bl6pSKm3+N9wpr3UwIdk7AbjPCUmNnGyj59+yHfC6l6m9
7lpa4r/b9/isgHC3YIs0ticYkCDojIkMzYO6FnSRTfFvsX6YclrcnGPdcGCyhOoS
Kk5nP8gI2pSopqHs6vQV2ELXOvzR8U0Yg8dPP6wsFgT4ir/t+UzM/ovcukhoKuMr
40+ZBYpQn3HFu0MVcYEZpmlshdQWIBNYzEVPubOKI9cla5UncjCWtnW9wRgTU/ip
8+758Q7oPRtfdg7tRNt1VM9wes1r9tKf4d6I2JqMSBPEVxZ+7IvwBnnX5r8YWx/d
uvWnezNAQHwt53rFF3T4ENbWfDtBLGT2b2KZTPlC/6UBMdfc8blWk/rvIeWRSa5K
OiEm/i80gBCS4WSSwZiS+8TMI38dpO+XxnC9PGsuVR4eDmxiekZGYwuWpPbjuRCl
xge0IXZEOj8/UM8zXuhIhp6A1v6JhnLELrx7AwhMzhiiCZDTQqIEGhbj0whc7igj
N0BbDAmdDZYMf3Uw2BID9IhWrJsnQ6BDJ2u5jGgO2CvNAlhvjYc=
=HJK9
-----END PGP SIGNATURE-----


More information about the Focal-changes mailing list