Bug 740635 - repoquery -g dies with traceback
Summary: repoquery -g dies with traceback
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: yum-utils
Version: 15
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-22 18:43 UTC by Chris Tyler
Modified: 2014-01-21 23:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-22 18:45:34 UTC


Attachments (Terms of Use)

Description Chris Tyler 2011-09-22 18:43:17 UTC
Description of problem:
repoquery dies with a traceback if used with the -g option

Version-Release number of selected component (if applicable):
1.1.31 -- this problem *does not* appear in 1.1.30

Steps to Reproduce:
1. run: repoquery -g -l base
  
Actual results:
$ repoquery -g -l base
Traceback (most recent call last):
  File "/usr/bin/repoquery", line 1406, in <module>
    main(sys.argv)
  File "/usr/bin/repoquery", line 1400, in main
    repoq.runQuery(regexs)
  File "/usr/bin/repoquery", line 990, in runQuery
    dot = self.options.dot)
  File "/usr/bin/repoquery", line 717, in doQuery
    return "\n".join(getattr(self, "fmt_%s" % method)(*args, **kw))
TypeError: fmt_list() got an unexpected keyword argument 'output'


Expected results:
$ repoquery -g -l base|head
yum-utils
openssh-clients
vconfig
dump
nss_db
acpid
sudo
...etc...

Comment 1 Chris Tyler 2011-09-22 18:45:34 UTC
geppetto reports this is closed upstream.


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