On Thu, 2004-05-20 at 11:53 +0200, Matthias Saou wrote: > Hi, > > I just ran "yum update" using a custom yum 2.0.7 packages, which got updated > to the Fedora Core 2 one, and all went fine. Right after, I ran "yum clean > all" as often since I'm short on disk space (my laptop), and to my surprise, > there was a damaged header (zero byte file) which made yum unhappy. Simply > removing it fixed the problem. > > Worth ignoring? Trying to fetch the damaged header file again and replace > it? Other ideas? > > Matthias > > -- > > [root@python2 root]# yum clean all > Gathering header information file(s) from server(s) > Server: Fedora Core 2 - i386 - Base > Server: Fedora Core 2 - i386 - Released Updates > Finding updated packages > Cleaning packages and old headers > Damaged Header /var/cache/yum/base/headers/epic-4-1.0.1-17.i386.hdr > Traceback (most recent call last): > File "/usr/bin/yum", line 30, in ? > yummain.main(sys.argv[1:]) > File "/usr/share/yum/yummain.py", line 296, in main > HeaderInfo, rpmDBInfo, obsoleted) > File "/usr/share/yum/clientStuff.py", line 1156, in take_action > clean_up_old_headers(rpmDBInfo, HeaderInfo) > File "/usr/share/yum/clientStuff.py", line 772, in clean_up_old_headers > (e, n, v, r, a) = getENVRA(hdr) > File "/usr/share/yum/clientStuff.py", line 67, in getENVRA > if header[rpm.RPMTAG_EPOCH] == None: > TypeError: unsubscriptable object > [root@python2 root]# > This one has been seen and i should fix it - knowing that it's a 0 byte file that causes it is very helpful. I think that is why it's slipping past the other try-except tests. thanks, -sv
