Bug 103359 - RPM update overwrites %{_libdir}/sasl/smtpd.conf
RPM update overwrites %{_libdir}/sasl/smtpd.conf
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: postfix (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: John Dennis
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-08-29 06:36 EDT by Peter Bieringer
Modified: 2007-04-18 12:57 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-09-09 10:27:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Peter Bieringer 2003-08-29 06:36:11 EDT
Description of problem:
A bug in spec file makes admins unhappy after updating postfix in cases they
changed the default sasl SMTP configuration and don't realize fast enough that
config was overwritten by update.

Version-Release number of selected component (if applicable):
postfix-1.1.12-1

How reproducible:
Always

Steps to Reproduce:
1. Change settings in %{_libdir}/sasl/smtpd.conf
2. Update postfix
3. Check content of %{_libdir}/sasl/smtpd.conf

Actual Results:  Reset to default by overwriting file

Expected Results:  File will be kept

Additional info:

Fix:

$ diff -u postfix-1.1.12-1.spec.orig postfix-1.1.12-1.spec
--- postfix-1.1.12-1.spec.orig  2003-08-29 12:28:00.000000000 +0200
+++ postfix-1.1.12-1.spec       2003-08-29 12:28:37.000000000 +0200
@@ -468,7 +468,7 @@
 %doc samples
 %doc README_FILES

-%{_libdir}/sasl/smtpd.conf
+%config(noreplace) %{_libdir}/sasl/smtpd.conf

 %dir %attr(0755, root, root) %verify(not md5 size mtime) %{_libexecdir}/postfix
 %{_libexecdir}/postfix/bounce
Comment 1 John Dennis 2003-09-09 10:27:51 EDT
Thank you for reporting this. It has already been fixed in the current rpm which
is 2.0.11-5.

Note You need to log in before you can comment on or make changes to this bug.