SP 2.0: Metadata with EncryptionMethod elements fails to load

Russ Allbery rra at debian.org
Tue Jan 20 21:54:31 UTC 2009

"Scott Cantor" <cantor.2 at osu.edu> writes:
> Russ Allbery wrote on 2009-01-20:

>> The reason why they're separated is because Debian Policy requires that
>> you be able to install multiple versions of a library with different
>> SONAMEs at the same time.

> That's not unusual, but I'm not sure why this works without a complaint
> on Red Hat. I've installed different versions of the libraries at the
> same time, minus the development files which shouldn't be allowed
> anyway.

I think RPM may allow multiple packages to own the same file.  I think I
recall seeing similar things in the past.  dpkg doesn't; having the same
file in multiple packages will prevent them from being installed at the
same time.

> That's why you might consider (as long as you're altering things)
> putting all the schemas into one package tied to the SP and avoid all
> the little connections.

Ah, pulling all of the xmltooling and opensaml2 schemas into the
shibboleth-sp2 source package and building one unified schema package that
it uses?  Hm.  That would avoid the versioning issues.  It's a little less
clean about what comes from where, and it would make our divergence from
the upstream shibboleth-sp2 release tarball a lot larger than just
removing the one file.

Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>

More information about the Pkg-shibboleth-devel mailing list