This bug was fixed in the package chrony - 4.2-0ubuntu1
---
chrony (4.2-0ubuntu1) jammy; urgency=medium
* Merge with Debian testing (LP: #1946848) and upstream v4.2.
Remaining changes:
- d/chrony.conf: use ubuntu ntp pool and server (LP 1744664 1754358)
- Set -x as
** Changed in: chrony (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946848
Title:
Merge chrony from Debian unstable for 22.04
To manage notifications
We are not much behind (one minor version atm) and often need to adapt
it late in the cycle due to the new glibc anyway. Therebe move this to
February just before the feature freeze.
** Changed in: chrony (Ubuntu)
Milestone: ubuntu-22.01 => ubuntu-22.02
--
You received this bug notification
** Description changed:
- Scheduled-For: 23.01
Upstream: tbd
- Debian: 4.1-4
+ Debian: 4.1-4
Ubuntu: 4.1-3ubuntu1
-
Debian does new releases regularly, so it's likely there will be newer
versions available before FF that we can pick up if this merge is done
later in the
** Changed in: chrony (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946848
Title:
Merge chrony from Debian unstable for 22.04
