[Pkg-crosswire-devel] Bug#796711: Bug#796711: sword: library transition is needed with GCC 5 as default

Daniel Glassey wdg at debian.org
Mon Aug 24 11:24:19 BST 2015

Thanks Julien,

A new version of the library (1.7.5) is imminent and will require a
transition anyway. So we'll start planning the transition to libsword12.


On Sun, Aug 23, 2015 at 4:18 PM, Julien Cristau <jcristau at debian.org> wrote:

> Source: sword
> Version: 1.7.3+dfsg-2.1
> Severity: serious
> Tags: sid stretch
> User: debian-gcc at lists.debian.org
> Usertags: libstdc++-cxx11
> Hi,
> sword's public API relies on types like std::string and std::list
> provided by libstdc++6, meaning that libsword11 needs to be renamed.
> Cheers,
> Julien
> The following is a form letter:
> 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,
> and 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.
> What is needed:
>  - Rebuild the library using g++/g++-5 from experimental. Note that
>    most likely all C++ libraries within the build dependencies need
>    a rebuild too. You can find the log for a rebuild in
>      https://people.debian.org/~doko/logs/gcc5-20150813/
>    Search for "BEGIN GCC CXX11" in the log.
>  - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
>    library API, and are used by the reverse dependencies of the
>    library.
>  - If there are no symbols matching __cxx11 or B5cxx11 in the symbols
>    forming the library API, you should close this issue with a short
>    explanation.
>  - If there are no reverse dependencies, it should be the package
>    maintainers decision if a transition is needed.  However this might
>    break software which is not in the Debian archive, and built
>    against these packages.
>  - If a library transition is needed, please prepare for the change.
>    Rename the library package, append "v5" to the name of the package
>    (e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you
>    have a soversion bump and you upload this version instead of the
>    renamed package.  Prepare a patch and attach it to this issue (mark
>    this issue with patch), so that it is possible to NMU such a
>    package. We'll probably have more than hundred transitions
>    triggered. Then reassign the issue to release.debian.org and
>    properly tag it as a transition issue, by sending an email to
>    control at bugs.debian.org:
>      user release.debian.org at packages.debian.org
>      usertag <this issue> + transition
>      block <this issue> by 790756
>      reassign <this issue> release.debian.org
>  - If unsure if a transition is needed, please tag the issue with help
>    to ask for feedback from other Debian developers.
> The libstdc++6 transition will be a large one, and it will come with a
> lot of pain.  Please help it by preparing the follow-up transitions.
> [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
> _______________________________________________
> Pkg-crosswire-devel mailing list
> Pkg-crosswire-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-crosswire-devel/attachments/20150824/c780789d/attachment.html>

More information about the Pkg-crosswire-devel mailing list