Re: yum traceback
"Steven H. Smith" <[email protected]>
| Newsgroups | gmane.linux.rpm.yum |
|---|---|
| Message-ID | <1238802656.3623.1.camel@shslaptop> |
Yum clean all did the trick. Thanks for the help! On Fri, 2009-04-03 at 15:08 -0400, James Antill wrote: > "Steven H. Smith" <[email protected]> writes: > > > did a yum update on CentOS 5.2 last night. Updated 530MB of packages, > > one which was rpm-4.4.2. Now I get the following error on yum update: > > > > > > Traceback (most recent call last): > [...] > > self._read_db_obj(db_obj) > > File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 94, in > > _read_db_obj > > setattr(self, item, _share_data(db_obj[item])) > > TypeError: unsubscriptable object > > This is the yum-metadata-parser error that's hitting a lot of > CentOS-5.2 updates (no idea why atm.) > > Fix for y-m-p is here: > > http://james.fedorapeople.org/yum/patches/yum-metadata-parser-1.1.2-no-updates.patch > > ...CentOS owners know about it and are likely to do an update. > Just run "yum clean metadata" to fix it in the short term. >