Bug 655838

Summary: php.spec for RHEL4 includes %config directives without noreplace
Product: Red Hat Enterprise Linux 4 Reporter: David Kutálek <dkutalek>
Component: phpAssignee: Joe Orton <jorton>
Status: CLOSED WONTFIX QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: low Docs Contact:
Priority: low    
Version: 4.8   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 16:16:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Kutálek 2010-11-22 14:01:02 UTC
Description of problem:

$ grep '%config' ./php-4.3.9-3.31.spec 
%configure \
%config(noreplace) %attr(644,root,root) %{_sysconfdir}/php.d/${mod}.ini
%config(noreplace) %{_sysconfdir}/php.ini
%config %{_sysconfdir}/pear.conf
%config %{_sysconfdir}/httpd/conf.d/php.conf

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

php-4.3.9-3.31

How reproducible:

Always

Steps to Reproduce:
1. install php srpm and grep spec for %config
2.
3.
  
Actual results:

pear.conf and httpd/conf.d/php.conf are overwritten when upgrading the package

Expected results:

no config overwritten

Additional info:

Comment 1 Joe Orton 2010-11-22 14:34:19 UTC
Ah, good catch.

They should only get overwritten because the spec file does not ensure that the timestamps of these files does not change across updates (when the contents are the same).  So we should fix both of these things.

Comment 2 Jiri Pallich 2012-06-20 16:16:59 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.