Ellis, Its likely your rpmdb is corrupt because the process was in the middle of making changes to it. You'll want to try rebuilding it. First delete the existing rpmdb cache files: rm /var/lib/rpm/__* then rebuild the db: rpm -vv --rebuilddb # I like using verbose so I know its doing something the db cache files will get recreated when you do your first rpm operation: rpm -qa Check for the db files: Hopefully doing a 'yum clean all' at this point should get you back to a good state. If not check the yum log for the last package it was working on and try downloading it and doing a Freshen on it explicitly. Russell On 6/11/06, Ellis Cohen <ellis_cohen@xxxxxxxxx> wrote: > > I was running "yum update" on my Fedora Core 4 box > and, for reasons having nothing to do with yum, > the process was aborted as it was running something > like the 70th of perhaps 150 transactions triggered > by the update. > > As a result, my impression is that my box is only > "partly" updated for a number of packages. > > But when I re-run yum, it doesn't do anything (and > apparently believes that the prematurely-terminated > update proceeded to normal completion). > > My question is: is there anything I can do to > make sure that my box is properly and completely > updated? I've looked at the yum manpage but don't > see the answer to this query. > > Thanks for any assistance! > > Ellis Cohen > > > _______________________________________________ > Yum mailing list > Yum@xxxxxxxxxxxxxxxxxxxx > https://lists.dulug.duke.edu/mailman/listinfo/yum > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.dulug.duke.edu/pipermail/yum/attachments/20060613/a9dce7eb/attachment.html
