** Changed in: freeipa (Debian)
Status: Unknown => 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/1778911
Title:
freeipa-client hard depends on chrony
To manage notifications
Looks like this was fixed in 4.7.1-1 in Debian, so this is fixed >=
Cosmic in Ubuntu.
If you need a fix for an existing stable release, please comment with a
justification against https://wiki.ubuntu.com/StableReleaseUpdates#When
and complete steps 1 through 4 in
Hi,
we are using ntp as a standard service, and it's deployed and configured by
puppet. So using chrony instead of ntp client is not really an option.
I just wanted to mention a dirty but possible quickfix to get around
this bug:
apt install freeipa-client # let it correctly solve all
I need a time daemon with server capabilities so we can easily monitor
clock skew.
Setting the dependency as recommends sounds like a great solution
indeed. Thanks for taking it into consideration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Currently we have these:
Reverse-Recommends
==
* ceph-base (for chrony)
This is the same case as with Freeipa.
* radioclk (for chrony)
This is meant to provide DCF77 input to chrony, so ok
Reverse-Depends
===
* freeipa-client
I agree that in a world of systemd-timesyncd by default packages could
stop depending on time-servers in most of the cases. But that is not a
bug in chrony but in freeipa.
Also it is not clear yet why your puppet would install one and then the
other, I'd ask you to file an extra bug with a bit