[JIRA] Commented: (SSPCPP-345) Split "package-level" and "user-level" settings in shib.conf to limit effect of RPM upgrades.
Scott Cantor (JIRA)
noreply at shibboleth.net
Mon Aug 22 14:33:27 BST 2011
[ https://issues.shibboleth.net/jira/browse/SSPCPP-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499#comment-13499 ]
Scott Cantor commented on SSPCPP-345:
-------------------------------------
Test packages available, per http://marc.info/?l=shibboleth-users&m=131377593400512&w=2
> Split "package-level" and "user-level" settings in shib.conf to limit effect of RPM upgrades.
> ---------------------------------------------------------------------------------------------
>
> Key: SSPCPP-345
> URL: https://issues.shibboleth.net/jira/browse/SSPCPP-345
> Project: Shibboleth SP - C++
> Issue Type: Bug
> Components: Installation
> Affects Versions: 2.3, 2.3.1, 2.4, 2.4.1
> Reporter: Benjamin Coddington
> Assignee: Scott Cantor
> Fix For: 2.5
>
>
> Automated rpm upgrades from the security:shibboleth repository replace /etc/httpd/conf.d/shib.conf, even though that file has been customized for the customer's application.
> The desired behavior is for the rpm to leave the current file intact, but this does not happen because there are new changes to the packaged shib.conf file each time an upgrade takes place, and those changes cause rpm to replace the file according to the rule explained here: http://www.rpm.org/max-rpm/ch-rpm-upgrade.html
> The changes to shib.conf for each upgrade are two alias lines for the logo image and css:
> --- shib.conf.R 2010-07-23 13:26:17.000000000 -0400
> +++ shib.conf 2010-12-14 17:09:19.000000000 -0500
> @@ -19,8 +19,8 @@
> <Location /shibboleth-sp>
> Allow from all
> </Location>
> - Alias /shibboleth-sp/main.css /usr/share/doc/shibboleth-2.3.1/main.css
> - Alias /shibboleth-sp/logo.jpg /usr/share/doc/shibboleth-2.3.1/logo.jpg
> + Alias /shibboleth-sp/main.css /usr/share/doc/shibboleth-2.4/main.css
> + Alias /shibboleth-sp/logo.jpg /usr/share/doc/shibboleth-2.4/logo.jpg
> </IfModule>
> Those lines always contain the new version number, so rpm always sees this file as needing to replace the current config file, which breaks our customized config file each time we upgrade.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the commits
mailing list