Bug 142129 - generate-rss command gives IndexError
Summary: generate-rss command gives IndexError
Status: CLOSED DUPLICATE of bug 138376
Alias: None
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
(Show other bugs)
Version: 3
Hardware: All Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-12-07 16:03 UTC by Joseph Wilhelm
Modified: 2014-01-21 22:50 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 19:07:35 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Joseph Wilhelm 2004-12-07 16:03:58 UTC
This is on a Fedora Core 3 installation; this package is fully
updated, version 2.1.11-3

Running the following command:
yum --rss-filename=foo.rss generate-rss

I get this error:
Traceback (most recent call last):
  File "/usr/bin/yum", line 8, in ?
  File "/usr/share/yum-cli/yummain.py", line 51, in main
  File "/usr/share/yum-cli/cli.py", line 245, in getOptionsConfig
    self.parseCommands() # before we exit check over the base command
+ args
  File "/usr/share/yum-cli/cli.py", line 340, in parseCommands
    self.extcmds[0] = 'recent'
IndexError: list assignment index out of range

It's easy enough to fix.. all I did was change line 340 to:
self.extcmds.append( 'recent' )

And now it works like a dream :)

Comment 1 Seth Vidal 2004-12-07 16:06:46 UTC
duplicate of 138376 and it's been fixed upstream but yum 2.1.12 has
not been released to fedore core 3 people yet <glare>

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

Comment 2 Joseph Wilhelm 2004-12-07 16:27:39 UTC
My apologies, I guess I should start searching the contents of the
bugs instead of just summaries.. it just happens there isn't a single
yum bug with "IndexError" or "index out of range" in the summary :)

Comment 3 Red Hat Bugzilla 2006-02-21 19:07:35 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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