Bug 437378
Summary: | cron issue for DOWNLOAD_ONLY=yes | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Bryan Gartner <bryan.gartner> |
Component: | yum-cron | Assignee: | Habig, Alec <ahabig> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | el5 | CC: | james.antill, mastahnke, tremble |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | ActualBug | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-09-23 08:44:11 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bryan Gartner
2008-03-13 19:04:42 UTC
yum-cron gets that functionality from "yum-downloadonly", you can just install that package yourself until then (it's available in 5.1 onwards). Note that makecache doesn't download any of the packages. Later versions of yum-cron (which I haven't been pushing to EPEL since yum-cron is a core CentOS package that we're not supposed to override in EPEL) fix this by requiring yum-downloadonly in the rpm requirements list. If you're interested in newer versions of this package, grab one out of an F-7 or newer repository. They'll work just fine on EL-5, we just can't push the updates there. Will change this to ASSIGNED and investigate the simultaneous export of a newer version to both EPEL and CentOS. (In reply to comment #1) > yum-cron gets that functionality from "yum-downloadonly", you can just install > that package yourself until then (it's available in 5.1 onwards). Okay, good to know, but shouldn't the yum-cron package then have such a dependency at the package level ? > Note that makecache doesn't download any of the packages. Good point, thanks for pointing that out (In reply to comment #2) > Later versions of yum-cron (which I haven't been pushing to EPEL since yum-cron > is a core CentOS package that we're not supposed to override in EPEL) fix this > by requiring yum-downloadonly in the rpm requirements list. Oops, guess I should have read all the replies. At least I know the reason now. > If you're interested in newer versions of this package, grab one out of an F-7 > or newer repository. They'll work just fine on EL-5, we just can't push the > updates there. > > Will change this to ASSIGNED and investigate the simultaneous export of a newer > version to both EPEL and CentOS. Thanks for all your help. Okay, so after checking again on the system in question, yum-downloadonly-1.0.4-3.el5 was already installed (with basically only RHEL and EPEL repositories accessible). I guess I am still a bit confused, and don't see a clear solution without enabling either CentOS or general Fedora repositories. Hmm - on the most comparable system I've got, FC6 (yum 3.0.6 and yum-downloadonly 1.0.3), things work for me. The yum-downloadonly package's whole purpose in life, from the rpm description, is: This plugin adds a --downloadonly flag to yum so that yum will only download the packages and not install/update them. so I'm puzzled why the plugin isn't doing what it claims. It's part of yum-utils, perhaps the yum-utils mother package isn't installed? Do you have any other yum plugins installed that do (or don't) work? Something to check. In /etc/yum.conf, do you have plugins enabled? ie, is plugins=1 somewhere in there? That's the default in Fedora, I'm not sure what it might be in EL-5. I've just followed the instructions in your report on a clean CentOS 5.5 box. * plugins=1 is the default * yum-cron does require yum-download * "/usr/bin/yum -e 0 -d 0 -y --downloadonly update" doesn't error On the grounds that over 2 years later Bryan hasn't replied, and I'm unable to reproduce the error, I'm going to close off the ticket. Bryan if this is still an issue feel free to reopen the ticket. |