Bug#620774: shibboleth-sp2: FTBFS everywhere: libshibsp.so: undefined references

[Russ Allbery]

Cyril Brulebois <kibi at debian.org> writes:

> your package FTBFS for its +b1 binNMU round, e.g. on i386:
> | /bin/bash ../libtool --silent --tag=CXX   --mode=link g++  -pthread -Wall -g -O2 -DNDEBUG -lsaml -lxml-security-c -lxmltooling -L/usr/lib -llog4cpp -lnsl  -o shibd shibd.o ../shibsp/libshibsp.la -lxerces-c
> | ../shibsp/.libs/libshibsp.so: undefined reference to `non-virtual thunk to xmltooling::AbstractPKIXTrustEngine::validate(x509_st*, stack_st_X509*, xmltooling::CredentialResolver const&, xmltooling::CredentialCriteria*) const'
> | ../shibsp/.libs/libshibsp.so: undefined reference to `xmltooling::AbstractPKIXTrustEngine::validate(x509_st*, stack_st_X509*, xmltooling::CredentialResolver const&, xmltooling::CredentialCriteria*) const'
> | collect2: ld returned 1 exit status
> | make[3]: *** [shibd] Error 1

> Full build logs:
>   https://buildd.debian.org/status/package.php?p=shibboleth-sp2

Yup, the Shibboleth packages are in the middle of a transition, and the
old shibboleth-sp2 package can't build against the xmltooling now in the
archive.  I just uploaded opensaml2, which is sitting in NEW due to the
upstream SONAME change, and then will upload a new shibboleth-sp2.

Sorry about the slowness of getting these packages updated.  I ran out of
time last week and let it sit for a bit.  I'll get shibboleth-sp2 uploaded
as soon as opensaml2 clears new and has had a chance to build.

Note, however, that anything that you were trying to do a binNMU for is
currently going to block on xmltooling on armel because of #619942.  I'm
not sure what to do about that.

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