Red Hat Bugzilla – Bug 209747
yumex no longer works with multiple repos
Last modified: 2007-11-30 17:11:45 EST
Description of problem:
If I have the normal fc6 test repos enabled (development and extras
development), when I try to run yumex all I get is a popup
that says: Error in loading repository data. This started
happening right after the yum-3.0-2 update was installed
(which fixed a bug it was having with multiple repos). Looks like
part of the fix needs to be done in yumex as well.
Version-Release number of selected component (if applicable):
Every time I run with more than one repo enabled.
Steps to Reproduce:
1. Start yumex with multiple repos enabled
2. See error popup
Updates to apply.
Bug 208778 was the yum bug who's fix seems to have busted yumex.
I cant reproduce the error.
1. Try to run 'yumex -n -d' from a console
2. Select 'Tools->Reset Repository Cache'
3. Select 'Refresh' in repo view.
4. Cut & paste the output from the console into a file and the to this report.
Created attachment 137979 [details]
debug output from yumex
look like there is somekind og problem with the yumex url cache, please attach
this file /var/cache/yum/yumex-mirror-cache.conf.
After attaching the file, try to delete it, to see if it is solves the problem.
Created attachment 137989 [details]
Here's the (very short) mirror cache file.
This file definitely seems a little light on content compared
to the corresponding file on my FC5 partition :-).
Created attachment 137990 [details]
The new version
Deleteing the old file and running yumex did indeed work, though the
new version out there now doesn't have a whole lot more in it than
the old one :-). I was definitely doing a lot of funny poking and
prodding of things when I had the original yum problem, musta got
busted in that process somewhere.
Ok, now i can reproduce it, there is no real content in the cache file, only
section headers. I it working if the section is availible, but it will do
mirrordetection every time.
I just have request a build of yumex 1.1.4 i fedora Extras Development.
It fixes the issue.
This is fixed in yumex-1.1.4.