Red Hat Bugzilla – Bug 190886
kyum destroys livna repos.
Last modified: 2007-11-30 17:11:32 EST
Description of problem:When you start kyum and then click the repository box for
the livan repos. All the livan repos are destoyed by their baseurl entries
being removed. Clicking livna-devel.repo destroys it. Clicking livna.repo seems
to destroy all the livna repos.
Version-Release number of selected component (if applicable):
How reproducible:every time
Steps to Reproduce:
2. Click on repositories tab
3. Click on the livna box.
Actual results: baseurls of livna.rep dissappear
Expected results: livna repo enabled or disabled
Additional info: A brief terst seemed to result in the livna repos are
the only ones distroyed
The reason this is happening seesm to be as follows. In other repos when more
than one basrurl is wanted a mirrorlist is referred to. In the livna repos the
baseurls are listed one after another separated by a carriage return.
Well it looks like kyum will not acdcespt that format and it removes everything
after the first carriage return. Seems to me this would be possible to fix with
a change in the osurce code and a recompile.
This bug is also noted in the upstream bug tracker:
In the bug listed above the creater on kyum says htis is not abig sice kyum
handles repos differently than yum or yumex. And he does not have time to fix it.
Well since he is a voluteer I can't force him to fix it. However, the format of
yum repos is a given. His excuse for saying this is not a bug is just plain
This bug is known as Bug #1362350 on sf.net
I hava add the bug #1084 on bugzilla.livna.org to suggest the use of a
mirrorlist tag instead of multiple URL in a BaseURL tag.
This is a strange solution to the problem. Livna is using a valid form for their
repo . It is kyum that insists on not accepting this valid repo format. So the
solution is to have livna change its repo form. If they will do that fine. But
really the problem is with kyum not livna, So it is kyum that should be fixed.
But again we can't force anyone to do osmething they don't want to do. And we
say GPL software don't cause problems.
I agree with comment #6. Our policy mirror so far has been to use main server
first (which has a 1Gbit/s ethernet link and peering connectivity with a bunch
of major French ISPs) and use mirrors as back up. The mirrorlist is commented in
the repo file and can be enabled at will.
Becouse this is a problem which should solve by the upstream author, I have
closed this bug.