Tom Diehl on 1 Dec 2003 06:44:02 -0500 |
On Mon, 1 Dec 2003, Paul wrote: > Rebecca Ore wrote: > > >On Sun, Nov 30, 2003 at 06:14:01PM -0500, Paul (emailme@dpagin.net) wrote: > > > > > >>Like I said, sometime RPM gets confused. By forcing a package to be > >>installed with --nodeps then removing the package, sometimes that > >>resolves the problem and allows the package to be installed the usual > >>way. I should have added that to my last message. > >> > >> > > > >Using the replace package option seems to be a perhaps safer way to do > >this when rpm's database is confused. Also, rebuilding the database > >isn't a bad idea either. How does rpm's database get "confused"?? What does this mean and how would --replacepkg help a "confused" db?? On certain older versions of rpm there was/is a file locking bug that required the removal of the lock files and rebuilding of the database. Is that what you are referring to?? If so I would suggest upgrading to the latest version of rpm for the applicable system. Look on rpm.org for the latest version. Red Hat never did an official update but JBJ put the updates on rpm.org for those who wanted to actually fix the problem. > What are the commands to replace a package and to rebuild the RPM database? --replacepkgs and --rebuilddb. There are the commands. Once again unless you have a good reason to use the --replacepkg command it should not be used. The only reason I know to use it is do downgrade a package. If you are not downgrading you do not need it. man rpm and/or www.rpm.org for more info. HTH, ..............Tom ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|