Red Hat Bugzilla – Bug 1269172
crontabs pulls in cronie which pulls in systemd which pulls in a bunch of other stuff
Last modified: 2016-11-24 09:10:14 EST
Description of problem:
tl;dr: installing less pulls in systemd
crontabs is described as a filesystem package: "The crontabs package contains root crontab files and directories.", but it requires /etc/cron.d, which is provided by cronie. This pulls in a whole slew of dependencies to be installed.
Please consider co-owning the /etc/cron.d instead.
Version-Release number of selected component (if applicable):
Why less requires crontabs? This looks suspicious.
It requires man-db, which requires crontabs.
Ah, that is a quite recent addition.
The question is whether having some crontab installed (such as the /etc/cron.daily/man-db.cron in case of man-db) does not also mean that you want to have it run. At least that was always the expectation. I understand that in case of some minimal cloud images the situation might be different. But in that case perhaps there should be something like dummy-crond package that would satisfy the /etc/cron.d dependency for cloud.
Other possibility would be to use weak dependency (Recommends) to pull cronie from crontabs.
This dependency doesn't actually enforce anything: it is always possible to have cronie installed and not enabled, or cronie installed and enabled, but systemd not running, in which case cronie doesn't run either. In this case I think the disadvantage of having a low-level tool like less pull in the whole stack is really high.
Dependencies are not there to enforce but to ensure that the user installing packages does not have to specify all the dependencies manually.
As I said the problem needs to be solved differently than by simply cutting the dependency.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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'
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 23 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.