Merge 4.1-3 for cleanups and glibc compatibility

[Christian Ehrhardt ]

4.1-3 has minor cleanups that are not important but nice.

Furthermore it has
     - Add allow-clone3-and-pread64-in-seccomp-filter.patch.
which we need for glibc 2.34 which is in proposed.

In addition to that we will also need https://git.tuxfamily.org/chrony/chrony.git/commit/?id=f27d719a4e2e983aea23058a29729a200b070dc6 for the new glibc.

Debian also accepted one of our Delta which can be dropped now.

[Christian Ehrhardt  (paelzer)]

FYI the ppa builds and tests are LGTM.
MP is here
  https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/407248
PPA:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4650/+packages

I'm waiting for an ack then I can upload

[Christian Ehrhardt  (paelzer)]

All good, uploaded to impish.

[Christian Ehrhardt  (paelzer)]

Now that I made the test work this leaves me stuck in proposed thanks to systemd.
But it is really odd - update-excuses lists them as failed:

chrony (4.1-1ubuntu1 to 4.1-3ubuntu1)
autopkgtest for systemd/248.3-1ubuntu4: arm64: Regression ♻ , armhf: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻

But if you look at the history of those architectures, there never was a test for chrony 4.1-3ubuntu1 ?!?

I think this asks for a restart and hopefully does not grow into anything more complex.

[Launchpad Janitor (janitor)]

This bug was fixed in the package chrony - 4.1-3ubuntu1

---------------
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

 -- Christian Ehrhardt <email address hidden> Tue, 17 Aug 2021 12:22:32 +0200