Control: affects -1 src:ntp
Am 13.01.20 um 02:02 schrieb Michael Biebl:
Hi Michael,
On Fri, 1 Jul 2005 13:49:45 -0400 Justin Pryzby
<justinpry...@users.sourceforge.net> wrote:
Package: chrony, ntp
Severity: normal
Only openntpd provides, conflicts, replaces: time-daemon.
Seems all NTP clients (ntpsec, chrony, openntpd) aside from ntp itself have
Conflict/Replaces/Provides: time-daemon
nowadays to prevent multiple implementations being installed and enabled
at the same time. This is a common mechanism defined in policy [1]
It's kinda annyoing that they all have to special case ntp and must
declare explicit Conflicts against ntp.
Would be great if you can reconsider this and consider adding
Conflict/Replaces/Provides: time-daemon
to ntp
Hrm, I wasn't involved in this discussion. Right now I don't see a major
blocker. There are a few packages that need time sync and only depend on
ntp without time-daemon (bwctl-server, lava, openstack-cloud-services,
openstack-compute-nodes), we should probably file bugs against them if
they only need some timekeeping facility.
I remember that some time ago some monitoring solutions also depended on
ntp to use and parse the output of ntpq or ntpdc, possibly on remote
servers. I only see hobbit-plugins doing that right now, and only using
Suggests.
Unless I find a major issue I'll do this in the next upload.
Bernhard
