shib.conf conflict

Russ Allbery rra at
Tue Oct 7 23:00:31 UTC 2008

Ferenc Wagner <wferi at> writes:

> 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.

Oh, right, because version 2 doesn't have any shib.conf, and when
Shibboleth 1 is removed by installing Shibboleth 2, it doesn't remove the
shib.conf file since the libapache2-mod-shib package isn't being purged,
just removed.

> 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/, as the two packages conflict.

Yup.  I think that's the right way to fix it.  Then, the a2dismod that
happens when libapache2-mod-shib removes the link for the config file and
the Shibboleth 2.0 package won't reintroduce it.

We should get this fix into lenny, which will mean making a lenny branch
off of the old master before we merged in Shibboleth 2.1.  I can take a
look at doing that.

Russ Allbery (rra at               <>

More information about the Pkg-shibboleth-devel mailing list