Red Hat Bugzilla – Bug 61853
up2date up2date screw old configuration file
Last modified: 2015-01-07 18:55:30 EST
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461) Description of problem: when you up2date up2date it rewrites you config file. I have specifically ignored certain groups of file ie. perl from being updated so as not to break my webserver. however after up2date updated it's self it removed the ignore perl section out of the config file. These mean that my nightly cron update caused perl to be downloaded and my webserver to crash. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.up2date up2date 2. 3. Actual Results: It rewrites the config file with the standard Expected Results: It should include any changes required to the config file but also keep packages which are specifically ignored Additional info:
Do you know if the old up2date config was setup to ignore possible file conflict issues? Generally, up2date wont update rpms if the status of the config files is in a state that may cause something to not work. It sounds like up2date was in this state (locally modified config, and a difference between old default and new default configs) so if --force or "noReplaceConfig" was setup, it would have overwrite the config file.
There were some rpm bugs that could result in the wrong version of a config file being used. These should be fixed with current releases.