Source: openimageio Version: 1.5.17~dfsg0-1 Severity: serious Justification: breaks reverse-dependencies
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 openimageio, 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/openimageio/openimageio_1.5.17~dfsg0-1ubuntu2.patch>. It also has unrelated Ubuntu changes, which is why I'm not tagging this "patch", but you might want to consider those changes as well. <https://bugs.debian.org/794702> will need to be fixed at the same time, and is also part of the Ubuntu 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 openimageio: * there is a circular build-dep with opencolorio which will need some care (Ubuntu temporarily disabled openimageio support in opencolorio, which seems a reasonable solution) * boost, opencv, openexr already started their transitions * Qt does not need a rename * I think the rest are C and so do not need renames so I think these two packages are ready to go. The package is likely to be NMU'd in the near future 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
