On Mon, Dec 07, 2020 at 11:05:56AM +0100, Miroslav Lichvar wrote: > On Fri, Dec 04, 2020 at 01:38:02AM +0100, Björn Persson wrote: > > > == Upgrade/compatibility impact == > > > > > > The `ntp` package is replaced automatically on upgrade to Fedora 34. > > > The configuration file ''/etc/ntp.conf'' is saved as to > > > ''/etc/ntp.conf.rpmsave'' and it needs to be renamed to > > > ''/etc/ntp.conf'' to be used by `ntpsec`. Otherwise, `ntpsec` will > > > fall back to the default configuration in ''/etc/ntp.d'' using the > > > ''pool.ntp.org'' servers. > > > > > > The `ntpd` service is disabled after the upgrade and needs to be enabled again. > > > > That's not so nice to those users who can use NTPsec as a drop-in > > replacement. For them it would be better to keep the configuration file > > and have the service enabled if it was enabled before the upgrade. > > Good point. What would be the best way to do that in the ntpsec > package? Trigger on ntp? Since the plan it to Obsolete the old package, I think you should trigger on the removal of it: %triggerun ntp <= ... # copy service enablement from the old name to the new name if systemctl is-enabled -q ntpd 2>/dev/null; then systemctl enable ntpsecd # if the name is different... fi ... Zbyszek _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
