wferi at niif.hu
Tue Oct 7 21:14:15 UTC 2008
Russ Allbery <rra at debian.org> writes:
> Ferenc Wagner <wferi at niif.hu> writes:
>> 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?
Because the version 2 module does not understand the ShibSchemaDir
directive. But the module loader names are the same, so a2enmod can
not differentiate: it links in the version 1 shib.conf together with
shib.load when it enables the version 2 module.
>> What do you think the best way would be to handle this unfortunate
> Fix whatever is causing the configuration file to break a different
> module, I think.
Which means renaming the version 2 module loader, I guess. That is,
use /etc/apache2/mods-available/shib2.load instead of
/etc/apache2/mods-available/shib.load. The module name can stay
/usr/lib/apache2/modules/mod_shib_22.so, as the two packages conflict.
More information about the Pkg-shibboleth-devel