Am Mi., 6. Dez. 2023 um 12:09 Uhr schrieb Ondrej Pohorelsky < opoho...@redhat.com>:
> > > On Wed, Dec 6, 2023 at 11:26 AM Michael J Gruber <m...@fedoraproject.org> > wrote: > >> Hi there, >> >> what is the impact of these changes: >> - Do default installs work the same way as before? >> - Do existing setups (crontabs) keep working? >> >> If yes then I'd consider the permission changes to be fixes, or at least >> standard packaging changes. >> >> What is is the policy for existing cron.allow/cron.deny, i.e. what would >> `rpmconf -a` tell me? >> >> > The default installs work same as before. > Existing crontabs keep working as usual. > > The only difference is that if you have populated the cron.deny list, > after update it gets saved as .rpmsave and cron.allow is created. > If the cron.deny is blank, it will get replaced. > Also, if you had cron.allow populated before, it will stay this way and > blank cron.allow.rpmnew is created. > > Thanks, that sounds like the typical things to expect during an upgrade. We typically don't even have release notes mentioning this, but it would be nice, since it's even a "plus" for F40 (compliance, hardening). Cheers Michael
-- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
