[Bug 1771061] Re: please merge new chrony 3.3 for Cosmic

2018-05-22 Thread Launchpad Bug Tracker 
This bug was fixed in the package chrony - 3.3-2ubuntu1

---
chrony (3.3-2ubuntu1) cosmic; urgency=medium

  * Merge with Debian unstable (LP: #1771061). 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
  - d/p/lp-1718227-nm-dispatcher-for-networkd.patch
  * Dropped changes
- debian/usr.sbin.chronyd: ensure RTC/GPS usage isn't blocked by apparmor
  (LP: 1751241) (in Debian now)
- debian/usr.sbin.chronyd: add cap net_admin for hwtimestamp (LP: 1761327)
  (in Debian now)
- d/p/lp1589780-sys_linux-don-t-keep-CAP_SYS_TIME-with-x-option.patch:
  When dropping the root privileges, don't try to keep the CAP_SYS_TIME
  capability if the -x option was enabled. This allows chronyd to be
  started without the capability (e.g. in containers) and also drop the
  root privileges (This is upstream now).
- d/p/lp-1718227-ignore-non-up-down-events-in-nm-dispatcher.patch (This is
  upstream now).
- d/control: switch to nss instead of tomcrypt (Debian switched to nettle
  which is in main, so we can drop this)
  * Added changes
- debian/README.container: fix typos

chrony (3.3-2) unstable; urgency=medium

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

  * debian/control:
- Bump standard-version to 4.1.4 (no changes required).
- Switch to the Nettle cryptographic library for hash functions.

  [ Helmut Grohne ]
  * debian/rules:
- Pass CC to make and set “--host-system” to fix FTCBFS. (Closes: #895852)

  [ Christian Ehrhardt ]
  * debian/usr.sbin.chronyd:
- Support all paths suggested in the man page.
(LP: #1771028, Closes: #898614)

chrony (3.3-1) unstable; urgency=medium

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

  * Merge branch “experimental” into “master”.

  * debian/copyright:
- Update copyright year.

  * debian/usr.sbin.chronyd:
- Allow CAP_NET_ADMIN to support HW timestamping. (LP: #1761327)

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

  * Import upstream version 3.3-pre1:
- Please see /usr/share/doc/chrony/changelog.gz for the release notes.

  * debian/copyright:
- Add “hash_nettle.c” copyright information and update copyright year of
test/unit/*

chrony (3.2-5) unstable; urgency=medium

  [ Christian Ehrhardt ]
  * debian/usr.sbin.chronyd:
- Allow write access to RTC, PPS and PTP devices.
(Closes: #891201, LP: #1751241)

 -- Christian Ehrhardt   Mon, 14 May
2018 09:06:01 +0200

** Changed in: chrony (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771061

Title:
  please merge new chrony 3.3 for Cosmic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1771061/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771061] Re: please merge new chrony 3.3 for Cosmic

2018-05-14 Thread  Christian Ehrhardt  
Pushed all related tags to ease review:
 * [new tag] lp1771061/deconstruct/3.2-4ubuntu4 -> 
lp1771061/deconstruct/3.2-4ubuntu4
 * [new tag] lp1771061/logical/3.2-4ubuntu4 -> 
lp1771061/logical/3.2-4ubuntu4
 * [new tag] lp1771061/new/debian -> lp1771061/new/debian
 * [new tag] lp1771061/old/debian -> lp1771061/old/debian
 * [new tag] lp1771061/old/ubuntu -> lp1771061/old/ubuntu
 * [new tag] lp1771061/reconstruct/3.2-4ubuntu4 -> 
lp1771061/reconstruct/3.2-4ubuntu4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771061

Title:
  please merge new chrony 3.3 for Cosmic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1771061/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771061] Re: please merge new chrony 3.3 for Cosmic

2018-05-14 Thread  Christian Ehrhardt  
Working fine for me in a bunch of tests from ppa:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3259

Proposing the merge now ...

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/345498

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771061

Title:
  please merge new chrony 3.3 for Cosmic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1771061/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771061] Re: please merge new chrony 3.3 for Cosmic

2018-05-14 Thread  Christian Ehrhardt  
TODO:
- 1744664 and 1754358 to be combined in changelog mentioning and commits
- 1761327 + 1751241 - Drop Delta (accepted in Debian)
- Patches we carried that we brought upstream in 3.3 (Drop)
  - e8096330 
debian/patches/lp1589780-sys_linux-don-t-keep-CAP_SYS_TIME-with-x-option.patch
  - b563048e 
debian/patches/lp-1718227-ignore-non-up-down-events-in-nm-dispatcher.patch
  - (the other one was post 3.3 and needs to stay for now)
- Rest stays but needs to be squashed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771061

Title:
  please merge new chrony 3.3 for Cosmic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1771061/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs