Red Hat Bugzilla – Bug 68696
Customized HTTP error messages are overwritten during upgrade
Last modified: 2014-03-16 22:28:49 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530
Description of problem:
First, this is a RedHat packaging error. Not a bug in squid.
Every time we upgrade squid we lose our locally customized error messages. This
has happened from as far back as we have been using the RedHat version of the
squid RPM, at least 6.0 I think. The files in /etc/squid/errors should be
designated as config files such that the vanilla ones from the RPM are created
as *.rpmnew instead of overwriting any changed files. I think they need to be
the specified the same as the /etc/squid/squid.conf file in the spec file.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Modify a file in /etc/squid/errors
2. Upgrade squid from an errata
Actual Results: All HTTP error messages revert to the plain-vanilla squid samples.
Expected Results: Our locally customized files should not be overwritten. The
plain-vanilla versions should be saved as *.rpmnew
If you want to customize them, make a new directory, and point the
/etc/squid/errors symlink there; the symlink should be preserved on upgrade.