Bug 117314

Summary: yum-2.0.5.20040229-1 problem = catch-22
Product: [Fedora] Fedora Reporter: Hans Christian Studt <hc>
Component: yumAssignee: Jeff Johnson <jbj>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:01:46 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 Hans Christian Studt 2004-03-02 19:57:52 UTC
Description of problem:
Today FC2T1 was updated to yum-2.0.5.20040229-1.
The problem is that now yum does not work, which mean I can not
receive a fixed version of yum (catch-22).

Version-Release number of selected component (if applicable
yum-2.0.5.20040229-1

How reproducible:
Always

Steps to Reproduce:
1. yum check-update
  
Actual results:
#yum check-update
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

Expected results:
Feching headers

Comment 1 Bart Martens 2004-03-02 20:01:51 UTC
*** Bug 117315 has been marked as a duplicate of this bug. ***

Comment 2 Jeff Johnson 2004-03-02 20:31:54 UTC

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

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