Bug 1296821 - Missing config(noreplace) macro for /etc/pam.d/samba in the spec file
Summary: Missing config(noreplace) macro for /etc/pam.d/samba in the spec file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: samba
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Andreas Schneider
QA Contact: Robin Hack
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-08 08:38 UTC by Jakub Hradil
Modified: 2016-11-04 06:58 UTC (History)
4 users (show)

Fixed In Version: samba-4.4.4-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 06:58:59 UTC
Target Upstream Version:

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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2468 0 normal SHIPPED_LIVE samba bug fix and enhancement update 2016-11-03 14:06:51 UTC

Description Jakub Hradil 2016-01-08 08:38:22 UTC 
Description of problem:
After updating samba, the custom changes made in /etc/pam.d/samba are lost. This is due to config(noreplace) macro not being used for this file in the spec file.


Version-Release number of selected component (if applicable):
samba-4.1.12

How reproducible:
Always

Steps to Reproduce:
1. Modify /etc/pam.d/samba
2. Run yum upgrade samba (assuming update is available)
3. See customized /etc/pam.d/samba replaced by the one distributed in rpm

Actual results:
/etc/pam.d/samba is always replaced by the one provided by the rpm package.

Expected results:
/etc/pam.d/samba should be kept intact, so that custom changes are retained.

Additional info:
Comment 6 errata-xmlrpc 2016-11-04 06:58:59 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2468.html
Note You need to log in before you can comment on or make changes to this bug.