On Wed, Jul 22, 2020 at 1:11 PM Adam Williamson adamwill@fedoraproject.org wrote:
On Wed, 2020-07-22 at 11:46 -0600, Chris Murphy wrote:
Is is possible there's a significant minority who have workflows that explicitly depend on chrony? If it's not possible, then I'd support the working group just making the substitution for Workstation 33.
We literally just got done rewriting https://fedoraproject.org/wiki/QA:Testcase_base_service_manipulation (and the automated version of that test) to use chronyd on the basis that it's a reliable service that we can rely on to exist in all tested editions :/
Find and replace? :D
@core services dnf-makecache.timer auditd.service plymouth-start.service
chrony isn't in either @core or @standard groups. It's in server-product and workstation-product (anaconda-tools and system-tools). But it may not be in Cloud, IoT, or CoreOS. I'm not sure.