Bug 521066

Summary: repoquery traceback: AttributeError: 'YumBaseQuery' object has no attribute 'setCacheDir'
Product: [Fedora] Fedora Reporter: Till Maas <opensource>
Component: yum-utilsAssignee: Seth Vidal <skvidal>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 10CC: azelinka, james.antill, maxamillion, mmalik, pmatilai, tim.lauridsen
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-10-12 16:12:32 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 Till Maas 2009-09-03 12:35:47 UTC
Description of problem:
repoquery returns a python traceback if I want to use it:
# repoquery foo
Traceback (most recent call last):
  File "/usr/bin/repoquery", line 853, in <module>
    main(sys.argv)
  File "/usr/bin/repoquery", line 790, in main
    if not repoq.setCacheDir(opts.tempcache):
AttributeError: 'YumBaseQuery' object has no attribute 'setCacheDir'


Version-Release number of selected component (if applicable):
yum-utils-1.1.23-1.fc10 (from updates-testing)
yum-3.2.23-3.fc10


How reproducible:
always

Steps to Reproduce:
1. repoquery foo
  
Actual results:
Python traceback

Expected results:
some useful info

Additional info:
this happens both as user and as root and also after running "yum clean all".

Comment 1 Tim Lauridsen 2009-09-03 12:56:37 UTC
I can reproduce the issue in F11, but it is fixed running again YUM-3_2_X HEAD
So it look like yum-utils should requere yum-3.2.24 (not yet released).
I should work in rawhide there contains patches from YUM-3_2_X HEAD.
i have requested an unpushed yum-utils-1.1.23 from F10 and F11.

Comment 2 seth vidal 2009-10-12 16:12:32 UTC
I believe this is currently fine in both f10 and f11  currently

If we release yum 3.2.24 for f10 then it'll be fine there if/when we push a yum-utils there.