Source: opensaml2 Version: 2.5.3-2.1 Severity: serious Justification: breaks reverse-dependencies Tags: patch
Background[1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. In the case of opensaml2, std::string appears in header files that get installed, so it seems very likely that a transition is needed. The transition consists of renaming the library package, adding a v5 suffix. A patch is available in Ubuntu, <http://patches.ubuntu.com/o/opensaml2/opensaml2_2.5.3-2.1ubuntu2.patch>. These follow-up transitions for libstdc++ are not going through exactly the normal transition procedure, because many entangled transitions are going on at the same time, and the usual ordered transition procedure does not scale that far. When all the C++ libraries on which this library depends have started their transitions in unstable if required, this library should do the same, closing this bug; the release team will deal with binNMUs as needed. In the case of opensaml2: * boost has started its transition * liblog4shib has started its transition * libxml-security-c-dev has started its transition * libxerces-c-dev is not believed to need a transition * xmltooling is believed to need a transition but has not started yet (I haven't got as far through the alphabet as filing a similar xmltooling bug yet) so I think you need to wait for xmltooling before proceeding. However, the maintainers are the same; please consider this advance warning of a similarly RC xmltooling bug, and if you fix xmltooling before I get that far with mass-bug-filing, please check this package next. The package is likely to be NMU'd when it becomes ready if there is no maintainer response, with a patch based on the one in Ubuntu. The release team have declared a 2 day NMU delay[2] for packages involved in the libstdc++ transition, in order to get unstable back to a usable state in a finite time. S [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition [2] https://lists.debian.org/debian-devel-announce/2015/08/msg00000.html
