On Sun, Jan 24, 2010 at 11:38:45PM -0600, James Antill wrote: > On Fri, 2010-01-22 at 23:06 -0600, Matt Domsch wrote: > > I ran into this once recently, when I hit Ctrl-C at an inopportune > > moment while yum was running on that window. Like you, thought it was > > the RPM database that was corrupt, and like you did the same thing to > > no effect. > > > > # yum clean all > > > > had no effect either. > > > > To resolve, I deleted all the contents of /var/lib/yum/. It's kind of > > heavyweight, but it resolved it. You may try simply deleting > > /var/lib/yum/history/* first, and see if that's sufficient (assuming > > you don't need to be able to have yum roll back completed transactions > > to some previous state). If not, try deleting yumdb/ there. > > > > There may be a better way to handle this, but I'll let the yum experts > > chime in then. > > I've seen one other case of this, and indeed it was the yum history DB. > We can certainly give a better message (running: yum history new, will > give you a new history DB). But it's annoying that it happens, as AFAIK > we are using sqlite transactions everywhere. > Matt/Jim ... was there anything weird like /var/lib/yum being on NFS or > anything like that? For me, /var/lib/yum is on local storage. I'm sure I did hit Ctrl-C at some point to try to break out of it while it was downloading packages. -- Matt Domsch Technology Strategist, Dell Office of the CTO linux.dell.com & www.dell.com/linux -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
