[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: The future of src:ntp



Am 18.01.22 um 19:44 schrieb Moritz Mühlenhoff:
Bernhard Schmidt <berni@debian.org> wrote:
However, development for ntp.org is slow, upstream still using BitKeeper
is cumbersome, and even the testsuite needs to be fixes on some
architectures for new releases. Both ntpsec and chrony are (from my POV)
the better alternatives now. To a point where I would rather use chrony
for new deployments, but I'm shying away from not using my own work
anymore for the lack of real-life testing.

Agreed, I think we should simply remove src:ntp at this point. Fedora
migrated existing installs to ntpsec it seems:
(https://fedoraproject.org/wiki/Changes/NtpReplacement

I think Fedora prefers chrony instead of ntpsec.

Fwiw, I'm with Marco here: If systemd-timesyncd (a simple SNTP client which is enabled by default) doesn't fit your needs, chrony is a great alternative.

If "ntp" the binary package would become a transitional package that installs chrony, that'd be fine with me if that eases the transition.

I'd also be ok if src:ntp would just be dropped and we document that in our release notes accordingly.

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


Reply to: