On Thu, Oct 07, 2004 at 01:20:11PM -0700, Olaf Olson alleged: > Garrick, > > Thanks for your assistance. > > I should have told you all of the story, before asking for advice, > however, instead of trying to avoid the embarrassment of what I have done. > > I had a power surge, which knocked out portions of my installation > (Yellow Dog Linux, 3.0.1, on a PPC, G3 B&W). I managed to recover a > great deal of my installation, but, improper backups resulted in only a > partial restore. I had used yum to upgrade the kernel from 2.4.22-2a to > 2.4.22-2g. Unfortunately, my restore brought back the 2a image. I can't > use yum to reinstall the 2g kernel, because yum still believes I have > it. In reality, of course, the kernel isn't there and still needs all of > the simple attention and automatic configuration that yum so easily > provides. > > So... what I am really looking for, I guess, is a way to whack yum on > the head so that it gets partial amnesia and forgets that I ever managed > to update the kernel. Is there a way to do that?? The strategy below should work great in this case. The solution is to whack rpm on the head, 'rpm -e --justdb --nodeps kernel-2.4.22-2g', then 'yum update kernel' will do the right thing. > Thanks in advance... > > Olaf > > Garrick Staples wrote: > > >On Thu, Oct 07, 2004 at 11:20:46AM -0700, Olaf Olson alleged: > > > > > >>>I attempted a search of the archives for word of such a tool, but > >>>didn't find it listed. Is there a way to reinstall a particular > >>>package that has been broken by a user who deleted part of the > >>>application? I can't yum remove it and yum update, of course, says it > >>>is up to date. > >>> > >>> > > > >In many cases, you can simply remove the rpmdb entry for this package and > >then > >yum will happily install it. > > > >rpm -e --justdb --nodeps packagename > > > >However, before you do that, you need to decide whether this action is > >safe for > >this particular package. Look at the scripts for the package, 'rpm -q > >--scripts packagename', understand that yum will _install_ (not upgrade) > >the > >package, and decide whether this package will do the right thing. You > >might > >also want to check for any triggers. Depending on what you find, You might > >decide to download the package and manually install it with --noscripts > >--notriggers. > > > > > > > >------------------------------------------------------------------------ > > > >_______________________________________________ > >Yum mailing list > >Yum@xxxxxxxxxxxxxxxxxxxx > >https://lists.dulug.duke.edu/mailman/listinfo/yum > > > > > _______________________________________________ > Yum mailing list > Yum@xxxxxxxxxxxxxxxxxxxx > https://lists.dulug.duke.edu/mailman/listinfo/yum -- Garrick Staples, Linux/HPCC Administrator University of Southern California -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.dulug.duke.edu/pipermail/yum/attachments/20041007/55c5aa55/attachment.bin
