chrony 3.5-9ubuntu1 source package in Ubuntu

Changelog

chrony (3.5-9ubuntu1) groovy; urgency=medium

  * Merge with Debian unstable (LP: #1878005). 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.
    - d/t/control: harden time-sources-from-dhcp-servers test for systemd change
      (LP: 1873031)
  * Dropped changes [in Debian now]
    - d/t/upstream-system-tests: stop chrony/systemd-timesynd before tests
    - d/t/upstream-system-tests: fix stderr in case services do not exist
    - Stop starting systemd-timesyncd in postrm. This is no longer relevant
      since systemd-timesyncd is a standalone package declaring
      Conflicts/Replaces/Provides: time-daemon. (Closes 955773, LP: 1872183)
    - d/postrm: Reinstate the remove target (LP: 1873810)

chrony (3.5-9) unstable; urgency=medium

  * debian/patches/:
    - Add allow-some-*time64-syscalls-in-seccomp-filter.patch. Needed for
    32-bit architectures with new system calls using 64-bit time_t.
    (LP: #1878005)

  * debian/tests/control:
    - Add needs-internet restriction to the upstream-simulation-test-suite
    test.

  [ Christian Ehrhardt ]
  * debian/tests/upstream-simulation-test-suite:
    - Skip if preparation steps fail.
    - Make preparation steps more verbose.

chrony (3.5-8) unstable; urgency=medium

  * debian/postrm:
    - Stop starting systemd-timesyncd in postrm. This is no longer relevant
    since systemd-timesyncd is a standalone package declaring
    Conflicts/Replaces/Provides: time-daemon. (Closes: #955773)

  [ Christian Ehrhardt ]
  * debian/tests/upstream-system-tests:
    - Stop chrony/systemd-timesynd before running these tests. (LP: #1870144)

chrony (3.5-7) unstable; urgency=medium

  * debian/chrony.maintscript:
    - Remove the /etc/NetworkManager/dispatcher.d/20-chrony conffile.

  * debian/control:
    - Support seccomp facility on riscv64. It should be noted that the system
    call filter will stay disabled by default on this architecture until
    Linux >= 5.5 hits unstable.
    - Bump libseccomp-dev build-dep to 2.4.3-1~ to provide seccomp facility on
    riscv64.
    - Break network-manager (<< 1.20.0-1~). Prior to this version,
    NetworkManager would not look for dispatcher scripts into
    /usr/lib/NetworkManager/dispatcher.d/.

  * debian/dirs:
    - Create the usr/lib/NetworkManager/dispatcher.d subdirectories.

  * debian/links:
    - Change the location of the NetworkManager dispatcher script.

  * debian/patches/:
    - Add allow-renameat2-in-seccomp-filter.patch. Required as the riscv64
    architecture does not support the rename() and renameat() system calls.

  * debian/rules:
    - Move the NetworkManager dispatcher script in
     /usr/lib/NetworkManager/dispatcher.d/.

 -- Christian Ehrhardt <email address hidden>  Wed, 20 May 2020 09:57:39 +0200