Bug 177406 - repoquery tracebacks with the --resolve option
repoquery tracebacks with the --resolve option
Status: CLOSED DUPLICATE of bug 177405
Product: Fedora
Classification: Fedora
Component: yum-utils (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Seth Vidal
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2006-01-10 08:24 EST by Sarantis Paskalis
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-01-10 08:26:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sarantis Paskalis 2006-01-10 08:24:37 EST
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 ?
  File "/usr/bin/repoquery", line 637, in main
  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):

How reproducible:

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

Additional info:

Fully updated FC-4 system.
Comment 1 Sarantis Paskalis 2006-01-10 08:26:05 EST

*** 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.