Bug 87731 - /etc/mail/Makefile should be considered a configuration file
/etc/mail/Makefile should be considered a configuration file
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: sendmail (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Florian La Roche
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-04-01 15:26 EST by H. Peter Anvin
Modified: 2007-04-18 12:52 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-04-04 13:31:09 EST
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 H. Peter Anvin 2003-04-01 15:26:30 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030211

Description of problem:
/etc/mail/Makefile frequently contains site-specific rules.  Current sendmail
RPMs will replace /etc/mail/Makefile on updates, and put the old one in
Makefile.rpmsave.  This means the administrator has to manually correct the
configuration after each update.

Instead, /etc/mail/Makefile should be marked as a configuration file, so that a
modified file isn't replaced automatically, but the new default is installed as
Makefile.rpmnew.


Version-Release number of selected component (if applicable):
sendmail-8.12.8-5

How reproducible:
Always

Steps to Reproduce:
1. Have customized /etc/mail/Makefile
2. Upgrade sendmail via RPM
3. Examine Makefile
    

Actual Results:  Makefile replaced; old Makefile in Makefile.rpmsave

Expected Results:  Makefile intact; new Makefile in Makefile.rpmnew

Additional info:

Thanks for dealing with the associated problem described in bug 86005.
Comment 1 Florian La Roche 2003-04-04 13:31:09 EST
I have changed this to config(noreplace).

greetings,

Florian La Roche
Comment 2 H. Peter Anvin 2003-04-05 16:19:15 EST
Thanks!!

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