Bug#797625: xmltooling: transition needed for g++-5 ABIs
smcv at debian.org
Mon Aug 31 22:46:48 UTC 2015
Justification: breaks reverse-dependencies
Background: 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 xmltooling, 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,
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 xmltooling:
* boost, log4shib and xml-security-c started their transitions already
* xerces-c is not believed to need a transition
* the rest seem to be C
so I think this sub-transition is good to go.
The package is likely to be NMU'd relatively soon 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 for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.
More information about the Pkg-shibboleth-devel