please merge new chrony 3.3 for Cosmic
Bug #1771061 reported by
Christian Ehrhardt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chrony (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
We want to get new changes of this early in the cycle and drop some Delta accepted by Debian in the meantime. So far our Delta is no big pain, so we should easily be able to- re-merge later this cycle if needed,
Related branches
~paelzer/ubuntu/+source/chrony:merge-cosmic-3.3-1
- Robie Basak: Approve
- Canonical Server: Pending requested
- git-ubuntu developers: Pending requested
-
Diff: 534 lines (+391/-5)13 files modifieddebian/README.container (+60/-0)
debian/changelog (+143/-0)
debian/chrony.conf (+18/-1)
debian/chrony.default (+4/-0)
debian/chrony.service (+2/-2)
debian/chronyd-starter.sh (+70/-0)
debian/control (+4/-1)
debian/docs (+1/-0)
debian/install (+1/-0)
debian/links (+5/-0)
debian/patches/lp-1718227-nm-dispatcher-for-networkd.patch (+66/-0)
debian/patches/series (+1/-0)
debian/postrm (+16/-1)
Changed in chrony (Ubuntu): | |
status: | New → In Progress |
To post a comment you must log in.
TODO: patches/ lp1589780- sys_linux- don-t-keep- CAP_SYS_ TIME-with- x-option. patch patches/ lp-1718227- ignore- non-up- down-events- in-nm-dispatche r.patch
- 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/
- b563048e debian/
- (the other one was post 3.3 and needs to stay for now)
- Rest stays but needs to be squashed