I know a bug similar to this one existed in previous versions but this is still present for me in version 2.0.5
When I load a kickstart file and click next to load the group information i get the following error
yum.YumBase.doConfigSetup failed, probably an invalid configuration file /etc/revisor/conf.d/revisor-f8-i386.conf
I have tried this with all of the included configurations with revisor all generate the same result.
Not sure btw if this is the right release the one i got fromt he fedora repo says 2.0.5 but not EL-5
Could you do:
{{{ yum -d9 -c /etc/revisor/conf.d/revisor-f8-i386.conf list }}}
and see if YUM is more verbose on what the error is?
the outcome of that command is
{{{ yum -d9 -c file:///etc/revisor/conf.d/revisor-f8-i386.conf list Traceback (most recent call last): File "/usr/bin/yum", line 29, in yummain.main(sys.argv[1:]) File "/usr/share/yum-cli/yummain.py", line 85, in main base.getOptionsConfig(args) File "/usr/share/yum-cli/cli.py", line 163, in getOptionsConfig disabled_plugins=opts.disableplugins) File "/usr/lib/python2.5/site-packages/yum/init.py", line 162, in _getConfig self._conf = config.readMainConfig(startupconf) File "/usr/lib/python2.5/site-packages/yum/config.py", line 659, in readMainConfig yumconf.config_file_age = os.stat(startupconf.config_file_path)[8] OSError: [Errno 2] No such file or directory: 'file:///etc/revisor/conf.d/revisor-f8-i386.conf'
}}}
Why do you not have revisor-f8-i386.conf? What files do you have in /etc/revisor/conf.d ?
I do it just does not recognize it
{{{ [andy@localhost ~]$ ls /etc/revisor/conf.d fedora-7-gold.cfg revisor-f7-x86_64.conf revisor-fc6-x86_64.conf fedora-8-gold.cfg '''revisor-f8-i386.conf''' revisor-rawhide-i386.conf revisor-c5-i386.conf revisor-f8-i386.conf~ revisor-rawhide-ppc.conf revisor-c5-ppc.conf revisor-f8-ppc.conf revisor-rawhide-x86_64.conf revisor-c5-x86_64.conf revisor-f8-x86_64.conf sample-full.cfg revisor-f7-i386.conf revisor-fc6-i386.conf sample-ks.cfg revisor-f7-ppc.conf revisor-fc6-ppc.conf sample-live-games.cfg
How about your SELinux setup? It's "No such file or directory" that YUM gives you... so...
SELinux is disabled so that should not be an issue not sure why it is doing this would uninstalling and re-installing do anything?
Fixed it by un installing revisor removing the folder in the /etc folder and doing a yum clean all and yum clean packages then reinstlaling it
Metadata Update from @ajamison: - Issue set to the milestone: 2.0.5 (EL-5)