cantor.2 at osu.edu
Tue Oct 7 21:09:06 UTC 2008
> > libapache2-mod-shib contains /etc/apache2/mods-available/shib.conf,
> > which is left behind when the package is eventually replaced by
> > libapache2-mod-shib2, breaking the latter.
> Why would it break the other module?
Different commands and settings. That file in RPM terms is a "protected"
config file. In the current packages, it's now preserved, but moved out of
the way to .rpmorig
> > What do you think the best way would be to handle this unfortunate
> > situation?
> Fix whatever is causing the configuration file to break a different
> module, I think.
Leaving 1.x SP Apache config in place will break the 2.0 SP in some cases.
Same issue as with the underlying SP config, they aren't compatible, merely
More information about the Pkg-shibboleth-devel