Description of problem: I noticed that man-db is the only package left on my installation requiring a a cron daemon. Seemingly pretty overkill, I began looking at alternatives. I noticed that arch uses [1] a systemd timer to update their man-db cache, which seems like a much simpler solution. It seems like this is a more effective way to handle the cache, given that systemd is running every where already, and some might not want crond around? It might make sense to eliminate the use of /etc/sysconfig as well, and just use the --quiet option as in arch. Administrators who want to override the behavior can of course do so natively with systemd, without ugly config files. [1] https://projects.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/man-db Thanks! Version-Release number of selected component (if applicable): 21, rawhide
Hello, thanks for the link, will take a look at it as soon as possible. There is the same request in https://bugzilla.redhat.com/show_bug.cgi?id=1138965. Jan
f22 https://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20141006/1402136.html f21 https://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20141006/1402130.html
*** Bug 1138965 has been marked as a duplicate of this bug. ***
man-db-2.6.7.1-8.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/man-db-2.6.7.1-8.fc21
Package man-db-2.6.7.1-8.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing man-db-2.6.7.1-8.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-12595/man-db-2.6.7.1-8.fc21 then log in and leave karma (feedback).
man-db-2.6.7.1-8.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
man-db-2.6.7.1-9.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/man-db-2.6.7.1-9.fc21
man-db-2.6.7.1-10.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/man-db-2.6.7.1-10.fc21
man-db-2.6.7.1-11.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/man-db-2.6.7.1-11.fc21
man-db-2.6.7.1-10.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
man-db-2.6.7.1-12.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/man-db-2.6.7.1-12.fc21
man-db-2.6.7.1-12.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
And man-db converted back to using cron daemon. So this bug is not fixed anymore.
Jan, can you explain why man-db reverted to use cron? i.e. where precisely timer units had issues for you? Would love to fix whatever is necessary so that man-db can migrate.
Lennart, there were no issues with systemd's timer itself. It was working perfectly. Local cache was regenerated. There were two reasons for reverting: 1) bz#1171450 2) the change adding explicit dependency on systemd ad 2) Content of a container does not have to depend on systemd. Well you don't need man-pages in container although. However as cron/timer is needed only for regeneration of local cache, systemd is too powerful for that from my point of view. Anyway I would like to see cache being regenerated by rpm triggers. Which are not yet in Fedora. They could come in F23.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Why is man-db still depending on crontabs? It should use systemd timer units instead.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.