Description of problem: If dnf is to replace yum, we need a replacement for yum-cron Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
@Neal, you should tell your usecases for yum-cron, some features already exits in dnf (timer based cache refresh)
One use case is notification of pending security updates in /etc/motd (or similar mechanism). See https://fedorahosted.org/cloud/ticket/62
I use yum-cron on unattended servers to automatically perform all updates.
Hello, thank you for the report. We'll take a look.
BTW, the more (real) (detailed) use cases you provide the better for you.
From Kevin Fenzi on the mailing list, a brief description of yum-cron functionality. Depending on how you configure it, it can: - Mail you a list of pending updates - Mail you a list of pending security updates only. - Download all updates (but not apply them) - Download security updates (but not apply them). - Download and also apply all or security updates and send you an email summary.
The use case for cloud images is: "When I log into my cloud image, I am presented with an informative message about pending updates, with the count of unapplied security updates highlighted."
For systems in a computer lab, the use case might be: - at a defined time every day (or night), system checks for security updates - log result of check - if security updates are pending, apply those updates - log result (if applied, if successful, if errors) - optionally send email summary on error - optionally send email summary also on success - on a less-frequent schedule, do the above, but for all updates. I know that there are similar systems like yum-updatesd to do similar things, but those tend to involve daemons which run all of the time. Or, like gnome-software, they presume an interactive user who is capable of making the decision to apply updates. These are both not desired.
A use case for a server system might be: - download and cache all updates as they become available - log and email weekly summary of unapplied bugfix/enhancement updates - log and email immediate notice of pending security updates - log and email daily notice of unapplied security updates
The basic functionality has been pushed upstream today but to do severity/security-specific bugs this has to wait until bug 850912 (bringing core functionality for handling advisories) is resolved.
This is something that it'd be nice to have a nice howto for, along with whatever other basic documentation.
Provied including mailing emitter, configuration, documentation, severity filtering and systemd timers in a series of patches concluded by 0bfd5c1 on the master branch. Also see bug 995537.
For reference: the DNF equivalent of yum-cron is a package called dnf-automatic.
(In reply to Ales Kozumplik from comment #13) > For reference: the DNF equivalent of yum-cron is a package called > dnf-automatic. Okay! Turning it on in my Rawhide system and we'll see what happens. :)
I see that dnf-0.6.1 is out. Is there a plan to release this for F21? (That'd be awesome.)
dnf-0.6.1-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/dnf-0.6.1-1.fc21
dnf-0.6.1-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.