Apache compilation warning

[Russ Allbery]

Ferenc Wagner <wferi at niif.hu> writes:

> Okay.  What about the following?  They sound reasonable, isn't there a
> way to suppress them?
>
> dpkg-shlibdeps: warning: symbol ap_register_output_filter used by debian/libapache2-mod-shib2/usr/lib/apache2/modules/mod_shib_22.so found in none of the libraries.
> dpkg-shlibdeps: warning: 58 other similar warnings have been skipped (use -v to see them all).

This is a limitation in dpkg-shlibdeps with Apache modules.  Those symbols
are provided by the Apache binary itself when the module is loaded, and
dpkg-shlibdeps has no way of knowing that.  For the time being, one has to
just ignore them.

> And something more mysterious:
>
> dpkg-shlibdeps: warning: dependency on libnsl.so.1 could be avoided if "debian/libapache2-mod-shib2/usr/bin/resolvertest debian/libapache2-mod-shib2/usr/lib/apache2/modules/mod_shib_22.so debian/libapache2-mod-shib2/usr/lib/libshibsp.so.1.0.0 debian/libapache2-mod-shib2/usr/lib/shibboleth/adfs.so debian/libapache2-mod-shib2/usr/bin/mdquery debian/libapache2-mod-shib2/usr/lib/shibboleth/adfs-lite.so debian/libapache2-mod-shib2/usr/sbin/shibd debian/libapache2-mod-shib2/usr/lib/libshibsp-lite.so.1.0.0" were not uselessly linked against it (they use none of its symbols).

This is a minor upstream buglet in one of the packages that Shibboleth 2.0
depends on.  libnsl is harmless but pointless on Linux, but required on
Solaris.  There's a way of writing the configure probe to not link against
it on Linux as well, if we can figure out the right package (I don't think
it's Shibboleth 2.0 itself, since I don't see any references to nsl in its
source tree; it's probably picking it up from a *.la file via libtool),
but it's not horribly important.

> One more thing: in the changes file the short description of all three
> packages is the same, as if the parenthesised part was chopped off.
> Maybe the new short description is too long, after all...

It is too long -- one way to fix it is to drop "authentication and" from
all the short descriptions, since Shibboleth isn't, strictly speaking, an
authentication system.  (You have to provide your own authentication
system and protect the IdP with it.)

Are the schemas required at build-time?

Also, the runtime library needs to be broken out into a separate
libshibsp1 package and libshib2-dev should be libshibsp-dev, matching the
new library name.  I can do this, but don't want to stomp on what you're
doing and create unnecessary conflicts.  Let me know when you've finished
what you have time for today and I'll start working on the rest.

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