Bug 161610 - repo-rss doesn't work with yum 2.3.x
repo-rss doesn't work with yum 2.3.x
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: 2005-06-24 15:51 EDT by Ignacio Vazquez-Abrams
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-27 06:25:24 EDT
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 Ignacio Vazquez-Abrams 2005-06-24 15:51:27 EDT
When trying to use repo-rss with yum 2.3.x the following traceback is generated
due to the change in how yum handles changelogs:

Traceback (most recent call last):
  File "/usr/bin/repo-rss.py", line 238, in ?
    main(options, args)
  File "/usr/bin/repo-rss.py", line 212, in main
    rssobj.doPkg(pkg, url)
  File "/usr/bin/repo-rss.py", line 110, in doPkg
    item = self.rsspkg(pkg, url)
  File "/usr/bin/repo-rss.py", line 136, in rsspkg
    for e in pkg.changelog:
TypeError: iteration over non-sequence
Comment 1 Seth Vidal 2005-06-27 01:45:38 EDT
can you give me the versions of yum and which release of repo-rss this is?

I can't make this happen on my yum 2.3.3 and repo-rss from cvs.

Comment 2 Ignacio Vazquez-Abrams 2005-06-27 01:59:59 EDT
This is with yum 2.3.2-7. Updating yum to 2.3.3-1 doesn't solve this. Where's
the CVS for repo-rss?
Comment 3 Seth Vidal 2005-06-27 02:04:01 EDT
I don't remember changing any code in repo-rss but cvs is available via the web

Comment 4 Ignacio Vazquez-Abrams 2005-06-27 06:25:24 EDT
Ah, I see the problem. It's on my end, not yours. Sorry about that.
Comment 5 Seth Vidal 2005-06-27 09:16:01 EDT
would you mind telling me what it was?

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