The best thing to do before you actually pull the trigger is to: rpm -Uvh --test something.rpm
Whenever I update perl-Mail-SpamAssassin, it complains that spamassassin-tools depends on perl-Mail-SpamAssassin. So I wind up having to use the --nodeps option: rpm -Uvh --nodeps something.rpm The sequence I use is : 1) perl-Mail-SpamAssassin-vers# 2) spamassassin-tools-vers# 3) spamassassin-vers# --Larry > -----Original Message----- > From: Theo Van Dinter > Sent: Wednesday, October 15, 2003 3:34 PM > To: Charles Gregory > Cc: 'SA' > Subject: Re: [SAtalk] Spamassassin updates > > > On Wed, Oct 15, 2003 at 02:59:58PM -0400, Charles Gregory wrote: > > And now that I look at it, that particular file is my > local.cf that I > > didn't want over-written! So does this mean it aborts, is half way > > done, or WHAT? Have I just munched my Spamassassin 2.44? > Could someone > > please post COMPLETE directions for updating my Red Hat 9 > SA 2.44 RPM > > to 2.60 as sson as possible, thanks! > > Dude. Get a grip. > > #1, always make a backup. > #2, upgrading from non-official RPMs to official RPMs should > work, but ymmv. > > rpm -Uvh spamassassin-2.60* perl-Mail-SpamAssasin-2.60* > > That should, theoretically, get rid of the 2.44 install and > upgrade you to 2.60. If you wanted to be sure, blow away the > 2.44 install first (rpm -e spamassassin), then run the above. > > -- > Randomly Generated Tagline: > "Menu Boy no be coward like shrimp, Menu Boy be brave like prawn." > - The Simpsons, "Lisa the Tree Hugger" > ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
