Bug 146150

Summary:	Update of bacula renames and overwrites config files
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Forgotten User G1kRg_CIZX <forgotten_G1kRg_CIZX>
Component:	Update Problems	Assignee:	Anna Maresova <anicka>
Status:	RESOLVED FIXED	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Major
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

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.