[ubuntu/impish-proposed] chrony 4.1-3ubuntu1 (Accepted)

[Christian Ehrhardt]

chrony (4.1-3ubuntu1) impish; urgency=medium

  * Merge with Debian unstable (LP: #1940252). Remaining changes:
    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 on 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/helper-functions: restart explicitly to fix test issues
  * Added changes:
    - d/p/lp-1940252-rtc-avoid-printing-and-scanning-time_t.patch: glibc 2.34
      compatibility

Date: Tue, 17 Aug 2021 12:22:32 +0200
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/4.1-3ubuntu1
-------------- next part --------------
Format: 1.8
Date: Tue, 17 Aug 2021 12:22:32 +0200
Source: chrony
Architecture: source
Version: 4.1-3ubuntu1
Distribution: impish
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Christian Ehrhardt <christian.ehrhardt at canonical.com>
Launchpad-Bugs-Fixed: 1940252
Changes:
 chrony (4.1-3ubuntu1) impish; urgency=medium
 .
   * Merge with Debian unstable (LP: #1940252). Remaining changes:
     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 on 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/helper-functions: restart explicitly to fix test issues
   * Added changes:
     - d/p/lp-1940252-rtc-avoid-printing-and-scanning-time_t.patch: glibc 2.34
       compatibility
Checksums-Sha1:
 c8782193f7b9d462c0f6ae0f5c44406522e19869 2444 chrony_4.1-3ubuntu1.dsc
 2b23680d18f4c9d9447b6b80bf4992f35c18495d 45772 chrony_4.1-3ubuntu1.debian.tar.xz
 504cfb05f29de9d0a86d8af11ffa8a35e0b77043 7634 chrony_4.1-3ubuntu1_source.buildinfo
Checksums-Sha256:
 65ba42428281972ec2d26126f110e24119c7d8b09d05f06afa95bad6bb26c190 2444 chrony_4.1-3ubuntu1.dsc
 e6b528b5a6497b43f4939d1ec92b4f3ed994bdf278da1a994b375b30a1d4290e 45772 chrony_4.1-3ubuntu1.debian.tar.xz
 73fdcbca89d5e03897023dcf3494974e31ab502ef522e736a5801af7c3c068c2 7634 chrony_4.1-3ubuntu1_source.buildinfo
Files:
 5db2b96021441c6ec83bf9516205da51 2444 net optional chrony_4.1-3ubuntu1.dsc
 cacc36616efade95a0308ea5ffb55c0f 45772 net optional chrony_4.1-3ubuntu1.debian.tar.xz
 233244ed0cd1eeb4cdc4933df3d2d2a2 7634 net optional chrony_4.1-3ubuntu1_source.buildinfo
Original-Maintainer: Vincent Blut <vincent.debian at free.fr>