Shibboleth Developers

["Scott Cantor" <>]

Bernd Oberknapp wrote on 2009-10-22:
> update succeeded. Adding obsoletes dependencies to the renamed packages
> probably would allow an automatic update of log4shib and xmltooling, too.

All of them would conflict, right? Not just those two...

> /etc/init.d/shibd and /etc/apache2/conf.d/shib.conf are replaced during
> the update. If the rules for protecting content are added to conf.d/
> shib.conf (as the secure example suggests) instead or vhosts.d (which I
> would recommend) this might be a problem, at least this should be
> documented.

Some issues are documented, and the shib.conf file has always historically
been hands-off until very recently when I finally marked it as
config(replace). So it still gets overwritten, but as of 2.2, it at least is
renamed out of the way.
        
Whether they're deleted depends on what the version you're
replacing/upgrading looks like. It's not really based on these packages,
because even though they're marked as config files now, if they weren't
before, the old package removal will do what it thinks it should do with
them based on what was in that specfile at the time.

The 2.2 version didn't include init script support on SUSE, and the
shib.conf file was not protected prior to 2.2.

If you describe what you were upgrading from, I can probably determine if
it's doing something it's not supposed to, but it will never do the right
thing until the starting point is new enough to match the behavior it has
now.

-- Scott