[ubuntu/jammy-proposed] chrony 4.2-0ubuntu1 (Accepted)

Christian Ehrhardt christian.ehrhardt at canonical.com
Mon Jan 10 07:40:14 UTC 2022


chrony (4.2-0ubuntu1) jammy; urgency=medium

  * Merge with Debian testing (LP: #1946848) and upstream v4.2.
    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.
  * Drop patches present in v4.2
    - d/p/allow-clone3-and-pread64-in-seccomp-filter.patch
    - d/p/fix-seccomp-filter-for-BINDTODEVICE-socket-option.patch
    - d/p/lp-1940252-rtc-avoid-printing-and-scanning-time_t.patch
  * Added changes:
    - d/t/upstream-simulation-test-suite: bump to the matching clknetsim

Date: Thu, 06 Jan 2022 14:51:22 +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/4.2-0ubuntu1
-------------- next part --------------
Format: 1.8
Date: Thu, 06 Jan 2022 14:51:22 +0100
Source: chrony
Architecture: source
Version: 4.2-0ubuntu1
Distribution: jammy
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Christian Ehrhardt <christian.ehrhardt at canonical.com>
Launchpad-Bugs-Fixed: 1946848
Changes:
 chrony (4.2-0ubuntu1) jammy; urgency=medium
 .
   * Merge with Debian testing (LP: #1946848) and upstream v4.2.
     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.
   * Drop patches present in v4.2
     - d/p/allow-clone3-and-pread64-in-seccomp-filter.patch
     - d/p/fix-seccomp-filter-for-BINDTODEVICE-socket-option.patch
     - d/p/lp-1940252-rtc-avoid-printing-and-scanning-time_t.patch
   * Added changes:
     - d/t/upstream-simulation-test-suite: bump to the matching clknetsim
Checksums-Sha1:
 865cc2c2e2efbea14ccd7b6b0b5a98712f75ccf3 2444 chrony_4.2-0ubuntu1.dsc
 0f5de043b395311a58bcf4be9800f7118afd5f59 578411 chrony_4.2.orig.tar.gz
 188ceaea3a061f0dcf71557f3aff71ad00667562 44888 chrony_4.2-0ubuntu1.debian.tar.xz
 aa12336c41933f28a7422bef9e7dc6eef567f3ad 7639 chrony_4.2-0ubuntu1_source.buildinfo
Checksums-Sha256:
 74b25fea5bdbcc20087dcd377dd7372a68efeade6a1eb53071ccbd2df7ac1245 2444 chrony_4.2-0ubuntu1.dsc
 273f9fd15c328ed6f3a5f6ba6baec35a421a34a73bb725605329b1712048db9a 578411 chrony_4.2.orig.tar.gz
 3cbf9a80726f3365ff286965eb634e0b179f40dffe3f6163c3cd2592a92772e5 44888 chrony_4.2-0ubuntu1.debian.tar.xz
 de23349c2d6c8bc75d057830bde52a1af051df7f77f8fa46f6bd7ffecefdf2f6 7639 chrony_4.2-0ubuntu1_source.buildinfo
Files:
 bf31f53234ff3564679599306250010a 2444 net optional chrony_4.2-0ubuntu1.dsc
 07282f8e76a4399d6c17009bb6345614 578411 net optional chrony_4.2.orig.tar.gz
 940dab046ef0092e3d77775c4c6169ff 44888 net optional chrony_4.2-0ubuntu1.debian.tar.xz
 b9986d7463d49401d003c236d77e71c5 7639 net optional chrony_4.2-0ubuntu1_source.buildinfo
Original-Maintainer: Vincent Blut <vincent.debian at free.fr>
Vcs-Git: https://git.launchpad.net/~paelzer/ubuntu/+source/chrony
Vcs-Git-Commit: 546c8365002957487eef6a0b65e3c830f5453a39
Vcs-Git-Ref: refs/heads/merge-4.2-jammy


More information about the jammy-changes mailing list