Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 203974 - The configuration file is replaced after upgrade
The configuration file is replaced after upgrade
Product: Fedora
Classification: Fedora
Component: php-eaccelerator (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Matthias Saou
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2006-08-24 15:13 EDT by Raoul
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-28 08:07:11 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 Raoul 2006-08-24 15:13:54 EDT
Description of problem:

After RPM upgrade the /etc/php.d/eaccelerator.ini config file is replaced,
instead of being ritten as eaccelerator.ini.rpmnew

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Matthias Saou 2006-08-28 04:47:09 EDT
I am confused. The current config file is tagged properly :

%config(noreplace) %{_sysconfdir}/php.d/eaccelerator.ini

Can you copy/paste the output of the yum or rpm transaction where that happened,
as well as confirm what version you had installed before that? Did you get a
.rpmsave file, or did you not edit the default configuration?
Comment 2 Raoul 2006-08-28 08:02:20 EDT
Matthias, I am deeply sorry for this false bug report. I had actually switched
to the original eaccelerator.ini and this is why I was confused. I realised this
after checking my /etc backups.
Previously I had added many custom comments in that file, but I actually didn't
use it, but had saved it in some other place.
Again, I am sorry and please close this false bug report.
Comment 3 Matthias Saou 2006-08-28 08:07:11 EDT
OK, closing :-)

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