Bug 117357 - yum has runtime error when trying to download new headers
Summary: yum has runtime error when trying to download new headers
Keywords:
Status: CLOSED DUPLICATE of bug 117290
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: rawhide
Hardware: i686
OS: Linux
high
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-03-03 07:13 UTC by orion
Modified: 2014-01-21 22:49 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:01:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description orion 2004-03-03 07:13:55 UTC
Description of problem: 
 
After my latest update (Feb 2nd) yum has stopped working. 
Typing "yum update" or something similar gets me a UnboundLocalError 
thrown by a bad python statement. 
 
Here's the stack dump: 
 
[root@glamdring root]# yum update 
 
Unable to find pid 
Gathering header information file(s) from server(s) 
Server: Fedora Core 1.90 - Development Tree 
Finding updated packages 
Downloading needed headers 
Traceback (most recent call last): 
  File "/usr/bin/yum", line 30, in ? 
    yummain.main(sys.argv[1:]) 
  File "/usr/share/yum/yummain.py", line 253, in main 
    clientStuff.download_headers(HeaderInfo, nulist) 
  File "/usr/share/yum/clientStuff.py", line 919, in download_headers 
    cachedbdict = returnCacheDBHeaders(nulist) 
  File "/usr/share/yum/clientStuff.py", line 901, in 
returnCacheDBHeaders 
    mi = cachedb.dbMatch() 
UnboundLocalError: local variable 'cachedb' referenced before 
assignment 
[root@glamdring root]# 
 
Version-Release number of selected component (if applicable): 
 
yum-2.0.5.20040229-1 
 
How reproducible: 
 
yum update 
 
Steps to Reproduce: 
1.update to the latest yum package 
2.type "yum update" 
3. 
   
Actual results: 
 
See section #1 
 
Expected results: 
 
I expect it to update my packages or tell me there are none to 
update. 
 
 
 
Additional info:

Comment 1 Daniel Malmgren 2004-03-03 09:12:24 UTC
Confirmed. 2.0.5.20040224-2 worked fine, 2.0.5.20040229-1 is a no-go.

Comment 2 Miloslav Trmac 2004-03-03 11:51:41 UTC

*** This bug has been marked as a duplicate of 117290 ***

Comment 3 Red Hat Bugzilla 2006-02-21 19:01:47 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


Note You need to log in before you can comment on or make changes to this bug.