Bug 230777 - TB3a4f1e9a __init__.py:237:reposSetup:TypeError: doRepoSetup() takes exactly 1 argument (2 given)
TB3a4f1e9a __init__.py:237:reposSetup:TypeError: doRepoSetup() takes exactly ...
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
i386 Linux
medium Severity urgent
: ---
: ---
Assigned To: Jeremy Katz
: 230827 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2007-03-02 15:11 EST by Julius B.
Modified: 2014-01-21 17:57 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-03-02 15:46:11 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 Julius B. 2007-03-02 15:11:22 EST
Description of problem:

nor yum neither software manager are doing _anything_.

Version-Release number of selected component (if applicable):

shipping with test 2 (upgraded from test 1)

How reproducible:


Steps to Reproduce:
1. start yum or software manager
Actual results:

Component: Software Manager
Summary: TB3a4f1e9a __init__.py:237:reposSetup:TypeError: doRepoSetup() takes
exactly 1 argument (2 given)

Traceback (most recent call last):
  File "/usr/sbin/pirut", line 462, in <module>
  File "/usr/sbin/pirut", line 458, in main
  File "/usr/sbin/pirut", line 360, in run
  File "/usr/sbin/pirut", line 380, in doRefresh
  File "/usr/lib/python2.5/site-packages/pirut/__init__.py", line 237, in reposSetup
TypeError: doRepoSetup() takes exactly 1 argument (2 given)

Local variables in innermost frame:
thisrepo: None
callback: <pirut.Progress.PirutProgressCallback instance at 0xa0ea84c>
self: <__main__.PackageManager object at 0xa053b0c>

Expected results:

window opening to install updates and/or software

Additional info:
Comment 1 Julius B. 2007-03-02 15:16:21 EST
sorry, it is not yum but it's pirut. yum IS working
Comment 2 Jeremy Katz 2007-03-02 15:46:11 EST
Actually, it's an API change in yum that shouldn't have happened.  Fixed in
upstream yum. I'll likely be pulling back a patch for this later today
Comment 3 Jeremy Katz 2007-03-03 08:58:53 EST
*** Bug 230827 has been marked as a duplicate of this bug. ***

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