RPM packaging problem - /etc/httpd/conf.d/shib.conf is overwritten on upgrade, but comments in file say "will be preserved across upgrades"
Basics
Technical
Logistics
Basics
Technical
Logistics
Description
Like a good little sysadmin I upgraded my SPs last night; today we discovered that the test SP was not functional.
I tracked this down to the /etc/httpd/conf.d/shib.conf being replaced with a new one. RPM created a .rpmsave of course. I'm sure it told me this but you know how it goes when you upgrade 20 machines, you're not looking at the output from each and every one in detail.
I'm sure this file is updated because the location of the css & jpg file changed with the new version number.
I'd prefer that config files not be replaced during an upgrade like this, but if they must be, they should have big fat comments telling the administrator not to modify them. Instead, it says:
RPM installations on platforms with a conf.d directory will
result in this file being copied into that directory for you
and preserved across upgrades.
Environment
RHEL5 x64 service4.internet2.edu (incommon test SP)
The explicit bug here is the broken comment in the file implying that shib.conf should be used for local changes, and the /secure example in the file, which makes it difficult not to touch it.
I can't allow for changes to the file and still guarantee Apache will start after an upgrade.
Like a good little sysadmin I upgraded my SPs last night; today we discovered that the test SP was not functional.
I tracked this down to the /etc/httpd/conf.d/shib.conf being replaced with a new one. RPM created a .rpmsave of course. I'm sure it told me this but you know how it goes when you upgrade 20 machines, you're not looking at the output from each and every one in detail.
I'm sure this file is updated because the location of the css & jpg file changed with the new version number.
I'd prefer that config files not be replaced during an upgrade like this, but if they must be, they should have big fat comments telling the administrator not to modify them. Instead, it says:
RPM installations on platforms with a conf.d directory will
result in this file being copied into that directory for you
and preserved across upgrades.