Bug 149496 - Yum dies with repoid not defined
Summary: Yum dies with repoid not defined
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
(Show other bugs)
Version: rawhide
Hardware: All Linux
medium
high
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-02-23 17:24 UTC by Steve Grubb
Modified: 2014-01-21 22:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-02-23 17:32:36 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Steve Grubb 2005-02-23 17:24:12 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041228 Firefox/1.0 Fedora/1.0-8

Description of problem:
I updated my rawhide installation with "yum update yum". Then I typed "yum check-update". This is what I got:

yum check-update
Traceback (most recent call last):
  File "/usr/bin/yum", line 7, in ?
    yummain.main(sys.argv[1:])
  File "/usr/share/yum-cli/yummain.py", line 51, in main
    base.getOptionsConfig(args)
  File "/usr/share/yum-cli/cli.py", line 151, in getOptionsConfig
    self.doConfigSetup(fn = conffile, root = root)
  File "__init__.py", line 70, in doConfigSetup
  File "__init__.py", line 121, in getReposFromConfig
  File "repos.py", line 103, in add
NameError: global name 'repoid' is not defined

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

How reproducible:
Always

Steps to Reproduce:
1. yum check-update

Actual Results:  NameError: global name 'repoid' is not defined

Expected Results:  A list of packages.

Additional info:

Comment 1 Jeremy Katz 2005-02-23 17:32:36 UTC
You have a duplicate repository id defined, workaround is to only have one repo
per id name.  Fixed in 2.3.0-2


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