Bug#797623: opensaml2: transition needed for g++-5 ABIs

[Russ Allbery]

Ferenc Wagner <wferi at niif.hu> writes:
> Russ Allbery <rra at debian.org> writes:

>> I think I was just confused and everything is fine, since the
>> transition already happened after the previous NMU.  There's still a
>> transition for opensaml2 and shibboleth-sp2, I think, but that's tiny
>> and not a big deal.

> Do you mean the library name transition (+v5), of which this bug is
> about?

I got confused and thought that we were uploading liblog4shib1v5 for the
first time, which would mean that everything would need to be rebuilt
against it so that the old library could be removed.  I'd missed that was
just incorporating an NMU, and liblog4shib1v5 had already been introduced.

We're still going to rename (+v5) opensaml2 per this bug, yeah, but that
only affects two packages, so it's not that big of a deal.

> Looks like it won't, the builds fail everywhere.  At first sight the
> problem seems to be that on amd64:

> checking if gcc static flag -static works... no

> which leads to liblog4shib.la being created, while on other arches:

> checking if gcc static flag -static works... yes

> and liblog4shib.la is not created, leading to an error when debian/rules
> tries to remove it.  While this would be easy to work around, I really
> wonder what's going on.  Looking at my older build logs, the -static
> flag occasionally worked on amd64, but most of the it does not work
> (according to configure).  Why does this happen?

The rm command for removing liblog4shib.la hard-coded the multiarch path
for amd64.  I just uploaded a new version of the package that should fix
it.

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