Denis Solovyov wrote: >>>I have NEVER seen any *.rpmnew. For example, a week or so ago there was >>>a postfix-conf upgrade. I don't use postfix, but keep the packages >>>installed. All files in /etc/postfix was silently overwritten without >>>any *.rpmnew. > > MS> RPM checks md5, not time. Since you never modified the default postfix > MS> configs, they were replaced with the new default configs. > > Vidar Tyldum Hansen said before that there was no md5 checking...
Of the binary files. I beleieve the checks are done on files where RPM has to evaluate whether to overwrite or not. > MS> If the md5 fingerprint of the old configuration is the same as was > MS> installed with the outgoing package, then there were no modifications to > MS> the old default configuration file. > MS> The upgrade package will replace an old default unmodified config with > MS> the new default config file. If the old config md5 does not match that > MS> of the old package installation, then you will see .rpmnew written > MS> during the upgrade. Timestamp does not affect md5: > > That's it! That is what I'm trying to say! I do NOT want swup to modify > my old (unmodified or at least "touched", i.e. with mtime or permissions > changed be me) default config to new default config. Is there any way to > "ask" swup to use such behaviour as I wish? (Or whom do I need to ask to > think about implementation of such behaviour in swup?) One way would be for you to add a comment in the config file or add some whitespace. I am still wondering if the reason you want this feature is either because of a bug in a package or misconfiguration. Do share with us the exact problems this is causing you.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
