Suddenly a problem with yum and yumex. It appears that when I invoke either I get an error message such as:
yum update yum Loading "skip-broken" plugin Loading "fastestmirror" plugin Options Error: Error parsing '3\t#2008.03.26': invalid integer value
I tried rm rpm /var/lib/rpm__db* which helped in the past but to no avail today.
Any suggestions welcome.
Bob Goodwin
Bob Goodwin wrote:
Suddenly a problem with yum and yumex. It appears that when I invoke either I get an error message such as:
yum update yum Loading "skip-broken" plugin Loading "fastestmirror" plugin Options Error: Error parsing '3\t#2008.03.26': invalid integer value
I tried rm rpm /var/lib/rpm__db* which helped in the past but to no avail today.
Any suggestions welcome.
Bob Goodwin
pup produces a more detailed error message which appears to stem from the same bit of corruption '3\t#2008.03.26':
Component: pirut Summary: TB65e8237b config.py:84:__set__:ValueError: Error parsing '3\t#2008.03.26': invalid integer value
Traceback (most recent call last): File "/usr/sbin/pup", line 611, in <module> main() File "/usr/sbin/pup", line 603, in main pup = PackageUpdater(not options.autoapply, options.config) File "/usr/sbin/pup", line 80, in __init__ GraphicalYumBase.__init__(self, False, config) File "/usr/lib/python2.5/site-packages/pirut/__init__.py", line 132, in __init__ plugin_types=(yum.plugins.TYPE_CORE,)) File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 116, in doConfigSetup errorlevel=errorlevel) 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 644, in readMainConfig yumconf.populate(startupconf._parser, 'main') File "/usr/lib/python2.5/site-packages/yum/config.py", line 401, in populate setattr(self, name, value) File "/usr/lib/python2.5/site-packages/yum/config.py", line 84, in __set__ raise ValueError('Error parsing %r: %s' % (value, str(e))) ValueError: Error parsing '3\t#2008.03.26': invalid integer value ................................ snip ...........................................
I am beginning to think about re-installing the system. This is F7, it may be time to install F8 in this box, I had hoped to wait for F9 ... But I need yum running if the system is to stay updated.
Does anyone have any idea of what may have happened, better yet how to restore things?
Bob Goodwin
Bob Goodwin wrote:
Bob Goodwin wrote:
Suddenly a problem with yum and yumex. It appears that when I invoke either I get an error message such as:
yum update yum Loading "skip-broken" plugin Loading "fastestmirror" plugin Options Error: Error parsing '3\t#2008.03.26': invalid integer value
I tried rm rpm /var/lib/rpm__db* which helped in the past but to no avail today.
Any suggestions welcome.
Bob Goodwin
pup produces a more detailed error message which appears to stem from the same bit of corruption '3\t#2008.03.26':
Component: pirut Summary: TB65e8237b config.py:84:__set__:ValueError: Error parsing '3\t#2008.03.26': invalid integer value
Traceback (most recent call last): File "/usr/sbin/pup", line 611, in <module> main() File "/usr/sbin/pup", line 603, in main pup = PackageUpdater(not options.autoapply, options.config) File "/usr/sbin/pup", line 80, in __init__ GraphicalYumBase.__init__(self, False, config) File "/usr/lib/python2.5/site-packages/pirut/__init__.py", line 132, in __init__ plugin_types=(yum.plugins.TYPE_CORE,)) File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 116, in doConfigSetup errorlevel=errorlevel) 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 644, in readMainConfig yumconf.populate(startupconf._parser, 'main') File "/usr/lib/python2.5/site-packages/yum/config.py", line 401, in populate setattr(self, name, value) File "/usr/lib/python2.5/site-packages/yum/config.py", line 84, in __set__ raise ValueError('Error parsing %r: %s' % (value, str(e))) ValueError: Error parsing '3\t#2008.03.26': invalid integer value ................................ snip ...........................................
I am beginning to think about re-installing the system. This is F7, it may be time to install F8 in this box, I had hoped to wait for F9 ... But I need yum running if the system is to stay updated.
Does anyone have any idea of what may have happened, better yet how to restore things?
Bob Goodwin
..........................................................................
I fixed the problem myself. I had added a line in /etc/yum.conf with a comment, the date, and the " # " wasn't being recognized as a comment? Removed that and things are normal again.
BobG