On Tue, 08 Jul 2008 13:37:27 -0500, Guy Ueland wrote:
> Did a yum update:
>
> yum updateTraceback (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=self.optparser._splitArg(opts.disableplugins)) File
> "/usr/lib/python2.4/site-packages/yum/__init__.py", line 162, in
> _getConfig startupconf.pluginconfpath,disabled_plugins) File
> "/usr/lib/python2.4/site-packages/yum/__init__.py", line 314, in
> doPluginSetup plugin_types, confpath, disabled_plugins) File
> "/usr/lib/python2.4/site-packages/yum/plugins.py", line 145, in __init__
> self._importplugins(types) File
> "/usr/lib/python2.4/site-packages/yum/plugins.py", line 186, in
> _importplugins self._loadplugin(modulefile, types) File
> "/usr/lib/python2.4/site-packages/yum/plugins.py", line 195, in
> _loadplugin conf = self._getpluginconf(modname) File
> "/usr/lib/python2.4/site-packages/yum/plugins.py", line 277, in
> _getpluginconf except ParsingError, e:NameError: global name
> 'ParsingError' is not defined Any ideas?
Well the current stable branch HEAD has:
except ConfigParser.ParsingError, e:
...a little after line 277, so I'd guess try that ... but that means you
have another error (just the yum error path has a bug in it) -- what
version of yum is this, and what plugins do you have installed?
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxxxxx
https://lists.dulug.duke.edu/mailman/listinfo/yum
