Bug 146150 - Update of bacula renames and overwrites config files
Summary: Update of bacula renames and overwrites config files
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Update Problems (show other bugs)
Version: Final
Hardware: x86-64 SuSE Linux 10.0
: P5 - None : Major
Target Milestone: ---
Assignee: Anna Maresova
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-27 13:36 UTC by Forgotten User G1kRg_CIZX
Modified: 2006-01-31 10:45 UTC (History)
0 users

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User G1kRg_CIZX 2006-01-27 13:36:52 UTC 
We were testing bacula, in order to put it into production as a backup solution. But the last security upgrade (issued around 25 of january/2006) broke our configuration, by renaming the existing config files and using the new ones as default.
This is not the desirable behavior, as a simple update would force the administrator to check each config file with the service down.
Wouldn't be more sensible to keep the config files and rename the new ones as "*.rpm.new"?
Comment 1 Anna Maresova 2006-01-31 10:45:57 UTC 
Fixed for 10.1 (all .conf files will not be replaced any more). I will take care for it also in next security updates for released distributions.