Just to be clear, if I rebuild this with the source packages from unstable with a new upstream version the rename is not necessary?
On 03/09/15, 08:21am, Simon McVittie wrote: > Source: libtorrent > Version: 0.13.2-1 > Severity: serious > Justification: breaks ABI without a package rename > Tags: sid stretch > User: debian-...@lists.debian.org > Usertags: libstdc++-cxx11 > > 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 libtorrent, std::string appears in functions that are > explicitly exported, so it seems very likely that a transition is needed. > The transition normally consists of renaming the > affected library packages, adding a v5 suffix (libtorrent14v5). > The 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. Please avoid doing this unless the new upstream version > is very low-risk. > > 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 libtorrent, the C++ libraries > are libcppunit and libsigc++, which have both had their renames > already; so this sub-transition is ready to start. > > The package might be NMU'd if there is no maintainer response. 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. > > Regards, > S > > [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition > [2] https://lists.debian.org/debian-devel-announce/2015/08/msg00000.html -- ⨳ PGP 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co
signature.asc
Description: Digital signature
