Bug 655838 - php.spec for RHEL4 includes %config directives without noreplace
php.spec for RHEL4 includes %config directives without noreplace
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: php (Show other bugs)
Unspecified Unspecified
low Severity low
: rc
: ---
Assigned To: Joe Orton
BaseOS QE - Apps
Depends On:
  Show dependency treegraph
Reported: 2010-11-22 09:01 EST by David Kutálek
Modified: 2012-06-20 12:16 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 12:16:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Kutálek 2010-11-22 09:01:02 EST
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):


How reproducible:


Steps to Reproduce:
1. install php srpm and grep spec for %config
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 09:34:19 EST
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 12:16:59 EDT
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.

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