-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jim Cornette wrote: > > The safest way to remove the older package remnants is to download the > newer packages and run > 'rpm -Uvh --replacepkgs --replacefiles packagename(s).arch.rpm' > because of the reasons that you pointed to. If the older package has > files that are the same name as used in the newer package, erasure of > the files is probable when you erase the older version of the rpm. > > Running 'rpm -Uvh --justdb --nodeps packagename(s).arch.rpm' will safely > only remove the database entry but will leave the documentation (has a > version number) and any files that are not contained within the new > package lingering on your system. But for most occasions that I seen, > each version of an rpm usually has files placed in the same location and > will differ only in date and other file characteristics. That is why > when you do an 'rpm -qV packagename' on the older package you usually > see a lot of output with file details being different and when checking > the later version you get no output because all is well with the newer > version rpm. > > I think so anyway! :-) > Jim > Thanks Jim When this happened previously, I found out when some new program being updated would not update the dependency or the program due to the older package. removing the older package from the db allowed the upgrade to progress. I might have an extra file or two running around on my machine, but it beats the hell out of not having a file or two! :-) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFFmASR5mBKdb7VQEcRAiIRAKCOmZKnaCHjxU/7X0wbkCsInV8B3QCfV0Sw kgjVNGiJPxZOYaH3tPj0Bdc= =Wtj3 -----END PGP SIGNATURE-----
