Created attachment 520428 [details] /var/log/up2date as referenced in error output from up2date command Description of problem: With EPEL-4 enabled on an RHEL-4 system, some 'up2date' attempts fail with header download errors relating to a(n apparently totally unrelated?!) header file for nagios, e.g.: # up2date cyrus-imapd-utils Fetching Obsoletes list for channel: rhel-i386-es-4... Fetching Obsoletes list for channel: dag... Fetching Obsoletes list for channel: EPEL... Fetching rpm headers... ######################################## Name Version Rel Arch ---------------------------------------------------------------------------------------- cyrus-imapd-utils 2.2.12 15.el4 i386 Testing package set / solving RPM inter-dependencies... Downloading headers to solve dependencies... There was an error downloading: http://download.fedoraproject.org/pub/epel/4/i386/headers/nagios-0-2.12-9.el4.i386.hdr There was an error downloading: http://download.fedoraproject.org/pub/epel/4/i386/headers/nagios-0-2.12-9.el4.i386.hdr There was an error downloading: http://download.fedoraproject.org/pub/epel/4/i386/headers/nagios-0-2.12-9.el4.i386.hdr There was an error downloading: http://download.fedoraproject.org/pub/epel/4/i386/headers/nagios-0-2.12-9.el4.i386.hdr There was an error downloading: http://download.fedoraproject.org/pub/epel/4/i386/headers/nagios-0-2.12-9.el4.i386.hdr An error has occurred: exceptions.UnboundLocalError See /var/log/up2date for more information Version-Release number of selected component (if applicable): Unknown; as far as I can tell, the current version of the nagios component for which up2date reports it cannot download a header file is actually 2.12.-10 (I guess this from looking at what files are available in an FTP listing of an EPEL-4 repository). How reproducible: How to get a system in to this situation in the first place, I do not know. On this particular system, simply having the EPEL 4 line added to the RHN sources file: yum EPEL http://download.fedoraproject.org/pub/epel/4/$ARCH is enough to cause it. Steps to Reproduce: 1. 2. 3. Actual results: Header download error above. Expected results: Normal up2date'ing. Additional info: /var/log/up2date file attached.
Can't reproduce because I don't have any EL-4 boxes anymore. Is this issue still valid?
Hi Peter. I was able to work around it, with substantial waste of time, and not consistently. At the moment, I do not have the problem, and of course hopefully I will soon not have any more RHEL4 boxes around either...