Even if yum-cron is told to do checks only, it will update yum if a new version
is available, because the line
/usr/bin/yum -R 120 -e 0 -d 0 -y update yum
...in the daily cron script is not guarded by CHECK_ONLY tests.
Also, the weekly cron script will do "yum clean packages" - I'm not sure if
that's desirable if CHECK_ONLY is set to yes.
I'd actually had the "update yum no matter what" line intentionally out of the
if/fi block, on the grounds that fixing broken stuff with the updater should be
the zeroth job an updater does. However, I agree that now that there is a way
to ask the thing to do a specific job, it should do as it's told. Will fix it.
Regarding yum clean packages. Yum does need to pick up after itself in the
/var/spool area, without the weekly cron script this never happens and it can
become quite bloated. However, one wouldn't want it blowing up freshly
downloaded packages if one had specified a check+download only usage.
Currently the cleanup will happen before the check+download, but yesterday's
check+download will still get wiped then re-downloaded, so the later in the week
the downloads happen the less time they'll reside on disk.
Any suggestions on how to best accomplish housekeeping without interfering with
downloading + human interaction?
I'd assume people who don't want to keep downloaded/installed packages around in
the cache just set keepcache=0 in their yum.conf. I haven't checked how that
setting works together with --downloadonly though.
yum-cron-0.6-1.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update yum-cron'
yum-cron-0.6-1.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.