[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

[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

[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

[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