Bug 177406 - repoquery tracebacks with the --resolve option
Summary: repoquery tracebacks with the --resolve option
Keywords:
Status: CLOSED DUPLICATE of bug 177405
Alias: None
Product: Fedora
Classification: Fedora
Component: yum-utils
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-01-10 13:24 UTC by Sarantis Paskalis
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-01-10 13:26:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Sarantis Paskalis 2006-01-10 13:24:37 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7

Description of problem:
repoquery crashes when supplied the --resolve option.  It works without it (it lists the individual capabilities).

# repoquery --requires --resolve gtk2
Traceback (most recent call last):
  File "/usr/bin/repoquery", line 640, in ?
    main(sys.argv)
  File "/usr/bin/repoquery", line 637, in main
    repoq.runQuery(regexs)
  File "/usr/bin/repoquery", line 409, in runQuery
    for p in self.doQuery(oper, prco): print p
  File "/usr/bin/repoquery", line 414, in doQuery
    return getattr(self, "fmt_%s" % method)(*args, **kw)
  File "/usr/bin/repoquery", line 444, in fmt_requires
    for res in self.whatprovides(req):
AttributeError: YumBaseQuery instance has no attribute 'whatprovides'


Version-Release number of selected component (if applicable):
yum-utils-0.3.1-1.fc4

How reproducible:
Always

Steps to Reproduce:
1. run repoquery --requires --resolve <packagename>
2. crash
3.
  

Additional info:

Fully updated FC-4 system.
rpm-4.4.1-22
yum-2.4.1-1.fc4
yum-utils-0.3.1-1.fc4

Comment 1 Sarantis Paskalis 2006-01-10 13:26:05 UTC

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


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