Bug#797994: synfig: ABI transition needed for libstdc++ v5
smcv at debian.org
Fri Sep 4 09:12:29 UTC 2015
Justification: breaks ABI without a package rename
Tags: sid stretch
User: debian-gcc at lists.debian.org
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 synfig, std::string appears in functions in public
headers, so it seems very likely that a transition is needed.
The transition normally consists of renaming the
affected library packages, adding a v5 suffix (libsynfig0v5).
The actual SONAME should not be changed when doing this.
If an upgrade to a new upstream SONAME is already planned, and that
SONAME has never been available in Debian compiled with g++-4, then an
alternative way to carry out the transition would be to bump the
SONAME. However, please avoid doing this unless the new upstream version
is very low-risk: the libstdc++ transition has stalled development in
unstable for long enough already.
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.
Looking at the build-dependencies of synfig:
* boost has already been renamed
* etl seems to be header-only so does not need a transition
* libmagick++ has already been renamed
* libmlt++ is not believed to need a transition (but please check)
so I think this sub-transition may be ready.
The package might be NMU'd if there is no maintainer response. 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-multimedia-maintainers