merge chrony 3.4 for disco

Bug #1802886 reported by Christian Ehrhardt  on 2018-11-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chrony (Ubuntu)
Undecided
Unassigned

Bug Description

Please update to the latest upstream
From parsing changelog things that come to mind are:

- policy respecting invoke
- Change default pidfile to /var/run/chrony/chronyd.pid to allow chronyd without root privileges to remove it on exit
- Improve example NetworkManager dispatcher script
- Add onoffline command to switch between online and offline state according to current system network configuration

  37 * debian/chrony.if-{post-down,up}:
  38 - Use the new “onoffline” command to tell chronyd to switch all sources to
  39 the online or offline status according to the current network configuration.

Drop:
dd patches to nm-dispatcher script for networkd-dispatcher: debian/patches/lp-1718227-nm-dispatcher-for-networkd.patch

d/p/lp-1787366-fall-back-to-urandom.patch: avoid hangs when starting the service on newer kernels by falling back to urandom
 d/p/lp-1787366-fall-back-to-urandom.patch: mention related Debian bug

squash
debian/README.container: fix typos

Related branches

Changed in chrony (Ubuntu):
status: New → Triaged
Launchpad Janitor (janitor) wrote :
Download full text (4.5 KiB)

This bug was fixed in the package chrony - 3.4-1ubuntu1

---------------
chrony (3.4-1ubuntu1) disco; urgency=medium

  * Merge with Debian unstable (LP: #1802886). Remaining changes:
    - d/chrony.conf: use ubuntu ntp pool and server (LP 1744664)
    - 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).
      + 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 chronyd-starter.sh available on install.
      + debian/docs, debian/README.container: provide documentation about the
        handling of this case.
    - d/postrm: re-establish systemd-timesyncd on removal (LP: 1764357)
    - Notify chrony to update sources in response to systemd-networkd
      events (LP: 1718227)
      + d/links: link dispatcher script to networkd-dispatcher events routable
        and off
      + d/control: set Recommends to networkd-dispatcher
  * Dropped Changes (upstream):
    - d/p/lp-1718227-nm-dispatcher-for-networkd.patch
    - d/p/lp-1787366-fall-back-to-urandom.patch: avoid hangs when starting
      the service on newer kernels by falling back to urandom. (LP: 1787366)
  * Added Changes:
    - d/postrm: respect policy-rc.d when restoring systemd-timesyncd
      (LP: #1771994)

chrony (3.4-1) unstable; urgency=medium

  * Import upstream version 3.4:
    - Please see /usr/share/doc/chrony/NEWS.gz for the release notes.

  * Merge branch “experimental” into “master”.

  * debian/chrony.service:
    - Conflict with ntpsec.service.

  * debian/copyright:
    - Update copyright years.

  * debian/patches/*:
    - Remove fix-samplefilt-unit-test-to-work-with-low-precision-clock.patch,
    fixed upstream.

chrony (3.4~pre1-2) experimental; urgency=medium

  * debian/patches/*:
    - Cherry-pick upstream patch to fix samplefilt unit test to work with
    low-precision clocks. This should prevent chrony from failing to build
    from source on HPPA and Alpha.

chrony (3.4~pre1-1) experimental; urgency=medium

  * Import upstream version 3.4-pre1:
    - Please see /usr/share/doc/chrony/NEW...

Read more...

Changed in chrony (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers