--On Wednesday, October 15, 2003 3:50 PM -0400 Charles Gregory <[EMAIL PROTECTED]> wrote:
> The docs say that 'local.cf' will not be affected by updates - it's the > "safe" place to put your local rules. Those error messages would seem to > suggest that is not quite true. That depends on how your existing RPM is set up. If it failed to define local.cf as a noreplace config file, but says that the RPM owns that file, then upgrading will remove it. The new RPM will not touch that file, but removing the old one (part of the update process) might. > "ymmv" - not familiar with that one..... Your mileage may vary. >> If you wanted to be sure, blow away the 2.44 install first >> (rpm -e spamassassin), then run the above. > > Yeah, I think I'll go that route. Thanks. Updates try to preserve config files common to the new and old package. The new package is installed, then obsolete files from the old package are removed. Use -Uvv and --test to verify that your config files are preserved, and backup anything that RPM isn't planning to. ------------------------------------------------------- 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
