Red Hat Bugzilla – Bug 451921
kyum fails to parse some repo files correctly
Last modified: 2008-06-24 06:45:10 EDT
Description of problem:
kyum fails to read ("parse"?) repository files correctly, when the format of
the repo file is like so:
In which case, kyum on the "Repository" tab shows for example (Note missing
name=Tigro for Fedora $releasever - $basearch
Also, any attempt to edit the repo file using kyum will blow away the "baseurl"
lines that are not displayed.
Note that this is a legal format according to yum's rules of syntax.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install kyum.
2. Install any repo file with above format.
3. Observe output as per example shown.
> kyum fails to read repo file and so no packages show up. Interestingly, the
missing baseurl/mirrorlist does not cause a failed "cannot retreive repo.xml"
or such (because yum itself does see those files?).
> kyum can effectively destroy a repo file by wiping out baseurl lines.
Correct parsing of "legal" repo files.
That bug exist as Bug #1785258 in the upstram bug reporting system.
I'm sorry, but it is patently obvious that this issue will not be fixed by the
There are at least two bugs open and unassigned on this issue, the oldest from
2005-11-20. In addition, no changes to the CVS source code have been made in
over two years. It is painfully clear that the author is either dead, disabled,
or has abandoned the project.
Please either address this issue with some solution, or remove the package from
circulation as it is broken, can't/won't be fixed, and presents a hazard to use.
Thanx and Regards,
OK, I have wrote a mail to the author about this topic. I have wrote, that the
package will been removed after a deadline, if they could not present any fixes
for the reported issues of the project.
Package is going to be retired, becouse the upstream autor has sent a quick
answer in which he wrote, that he has no time to maintain the project.
Thank You. Obviously, this is not the preferable outcome. However, in lieu of a
fix, I believe that it's better to retire the package than to leave it broken,
and to continue to grow more stale and potentially harmful to users. I
appreciate your taking action on this matter.
Thanks Again and Regards,