At least with DOWNLOAD_ONLY=yes, yum-cron says "New updates available" and "Updates downloaded, ..." even when there is an error downloading/accessing repos/dependency issues. This is with 0.8.4 on F-11, and also with 0.9.1 locally rebuilt for it. For example: ---- # /etc/cron.daily/0yum.cron New updates available for host $host kmod-em8300.i586 0.17.3-1.fc11.10 rpmfusion-free-updates kmod-em8300-2.6.30.9-90.fc11.i586-0.17.3-1.fc11.10.i586 from rpmfusion-free-updates has depsolving problems --> Missing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i586 is needed by package kmod-em8300-2.6.30.9-90.fc11.i586-0.17.3-1.fc11.10.i586 (rpmfusion-free-updates) Error: Missing Dependency: kernel-uname-r = 2.6.30.9-90.fc11.i586 is needed by package kmod-em8300-2.6.30.9-90.fc11.i586-0.17.3-1.fc11.10.i586 (rpmfusion-free-updates) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest Updates downloaded, use "yum -C update" manually to install them. ---- I'd expect yum-cron to not say "updates downloaded" when no updates were in fact downloaded, and instead of "New updates available" to say something like "Error checking for updates" if an error occurred.
You're right, we don't check the exit status for yum, figuring that yum's own error output would be self-explanatory, and that by asking for DOWNLOAD_ONLY, the user plans on manual intervention anyway. There are new updates available, that's correct (in this case, at least) - the problem is that the the instructions for applying them are bogus since the deps failed and it didn't actually download them. I can work on making this prettier. Will replace the line "Updates downloaded, use "yum -C update" manually to install them." with "Error checking for updates, see above for details." in the case of yum returning an error code.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Finally got a chance to implement this, and found an oddity. In the event "yum --downloadonly" gets things successfully, it returns an exit code of "1" for some reason. Which is also the code yum throws if something's gone wrong. So, due to this yum-downloadonly plugin weirdness, I'm not sure if there's a way for a script to tell if something barfed. Checking with that author to be sure.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 WONTFIX if it remains open with a Fedora 'version' of '12'. 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 prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Still haven't heard about how to better interpret yum-downloadonly return codes, keeping this open till we know and can trap it.
I don't think plugins can do anything about the yum exit status at the moment but to cause an exit with status 1; I've just submitted a patch upstream that (if accepted) could allow it in the future. http://lists.baseurl.org/pipermail/yum-devel/2010-November/007625.html Meanwhile, unfortunately I believe the only thing that could be done about this would be to catch --downloadonly's stderr (and/or out?) and look for the string "exiting because --downloadonly specified" in it :(
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping