On Sat, 13 Jul 2002, Greg Zartman wrote: > Lets say that I write an RPM and name it GJZ.XXX.XXX.rpm. Later a few > others put in their two cents and the rpm gets renamed to > devinfo.xxx.xxx.rpm. When users attempt to upgrade the GJZ rpm to the > devinfo rpm, a conflict will very likely occur. In fact, I had this very > thing happen recently. When I asked the lead developer what needed to be > done to resolve the conflict, he told me to use the --force option. :-(
another solution is to rename the rpm to a form matching the earlier installed package before installing it. Much better than force anyway as you can then rpm -Uvh properly. -=-=-==-=-=--=-=-=-=-=-=-=-=-=-=-=-= Graeme Robinson - Graenet consulting www.graenet.com - internet solutions -=-=-=-=-=-=-=-=-=-=-==---=-=--=-=-= -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
