Source: libosl Version: 0.6.0-3.2 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 libosl, 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 containing libosl.so.1 from "libosl1" to "libosl1v5". A patch is available in Ubuntu, <http://patches.ubuntu.com/libo/libosl/libosl_0.6.0-3.2ubuntu3.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 libraries on which libosl depends have started their transitions if required, libosl should do the same, closing this bug; the release team will deal with binNMUs as needed. In the case of libosl, libcppunit-dev and Boost have already started their transitions, so libosl seems to be ready to start too. The package is likely to be NMU'd in the near future, with a patch very similar to 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
