From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114 Description of problem: I logged in as root to do a 'yum upgrade', and I get the following traceback: Gathering header information file(s) from server(s) Server: Fedora Core 1 - i386 - Base Traceback (most recent call last): File "/usr/bin/yum", line 60, in ? yummain.main(sys.argv[1:]) File "yummain.py", line 188, in main File "clientStuff.py", line 766, in get_package_info_from_servers File "clientStuff.py", line 103, in HeaderInfoNevralLoad ValueError: unpack list of wrong size Version-Release number of selected component (if applicable): 2.0.4-2 How reproducible: Always Steps to Reproduce: 1. run 'yum upgrade' 2. wait 3. ka-boom Actual Results: traceback from python with a ValueError, as noted in description. Expected Results: expected some sort of timeout error, and move on to next mirror in list. Additional info: this problem appears to be triggered while getting headers from the redhat.com repo. yum crashed before it moved to the mirrors I have configured /etc/yum.conf with. in my testing, I ran 'yum upgrade' a 2nd time to try to duplicate the problem, and it crashed with the same traceback after a couple of minutes delay.
this appears to be a problem with the redhat.com repo. when I commented out the appropriate lines in /etc/yum.conf, the upgrade command runs just fine.
I now get this same error when using the 'muohio.edu' repo when using the 'check-update' command. the 'base' seems to be fine, but the 'updates' is what crashes. same line/function as with the redhat.com repo.
Created attachment 97073 [details] yum.conf file from quark
I was also getting this error, using the redhat repository as well as various mirrors. But the config file from http://fedora.artoo.net/faq/samples/yum.conf seems to work fine. See also http://www.redhat.com/archives/fedora-list/2004-January/msg03379.html (although the section about adding multiple "baseurl=" statements for a single repository seems incorrect -- see the yum.conf man page).
This problem appears to be transient, i.e. network and/or server related, not the yum client.