https://bugzilla.redhat.com/show_bug.cgi?id=2350109 --- Comment #46 from Alexandre Detiste <alexandre.detiste@xxxxxxxxx> --- Hi, Upstream talking here. > - Is the cron-update.{path,service} needed? Yes, absolutely. Vixie-Cron or Cronie will either watch these location with some os-provided facility (iselect()...) or poll these every minute. Also, when systemd-cron's "crontab" modify files in /var/spool...; it does not communicate with the generator and can not anyway. The current `systemctl daemon-reload` is the only way to refreh correclty & only once. > "Provides:" On Debian we have this nice things called "cron-daemon" & "cron-daemon-common" 'cron-daemon' is a so-called _virtual package_ provided by either vixie-cron/cron/systemd-cron. Theses three mutual implementation will also Conflicts: on 'cron-daemon' to avoid that the system explode. Random package needing some cron implementation will then depends on virtual package cron-daemon 'cron-daemon-common' is a runtime package shared by the 3 different crons and it contains the tmpfiles, sysusers.d and /etc/crontab stuff. Fedora has "crontabs" that fill a similar purpose. https://packages.fedoraproject.org/pkgs/crontabs/crontabs/ > I think this needs to be addressed > > Provides: cronie > Provides: cronie-anacron > Conflicts: cronie > Conflicts: cronie-anacron I joted this together 10 years ago. In practice if packages in Fedora Depends: on "cronie" and nothing else that makes systemd-cron uninstable. > The specfile really needs to be upstream... things would be easier... That's not how it works. Upstream should not be bothered after each 50 attemps to nudge a specfile in the right direction. I'm considering removing this contrib/ file altogether as soon as this package is accepted. Acceptiong tiny tmpfiles/sysusers sutff would be ok. Greetings -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component https://bugzilla.redhat.com/show_bug.cgi?id=2350109 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202350109%23c46 -- _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-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/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
