<div dir="ltr"><div><div><div>Thanks Julien,<br><br></div>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.<br><br></div>Regards,<br></div>Daniel<br><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Aug 23, 2015 at 4:18 PM, Julien Cristau <span dir="ltr"><<a href="mailto:jcristau@debian.org" target="_blank">jcristau@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Source: sword<br>
Version: 1.7.3+dfsg-2.1<br>
Severity: serious<br>
Tags: sid stretch<br>
User: <a href="mailto:debian-gcc@lists.debian.org">debian-gcc@lists.debian.org</a><br>
Usertags: libstdc++-cxx11<br>
<br>
Hi,<br>
<br>
sword's public API relies on types like std::string and std::list<br>
provided by libstdc++6, meaning that libsword11 needs to be renamed.<br>
<br>
Cheers,<br>
Julien<br>
<br>
The following is a form letter:<br>
<br>
Background [1]: libstdc++6 introduces a new ABI to conform to the<br>
C++11 standard, but keeps the old ABI to not break existing binaries.<br>
Packages which are built with g++-5 from experimental (not the one<br>
from testing/unstable) are using the new ABI. Libraries built from<br>
this source package export some of the new __cxx11 or B5cxx11 symbols,<br>
and dropping other symbols. If these symbols are part of the API of<br>
the library, then this rebuild with g++-5 will trigger a transition<br>
for the library.<br>
<br>
What is needed:<br>
<br>
- Rebuild the library using g++/g++-5 from experimental. Note that<br>
most likely all C++ libraries within the build dependencies need<br>
a rebuild too. You can find the log for a rebuild in<br>
<a href="https://people.debian.org/~doko/logs/gcc5-20150813/" rel="noreferrer" target="_blank">https://people.debian.org/~doko/logs/gcc5-20150813/</a><br>
Search for "BEGIN GCC CXX11" in the log.<br>
<br>
- Decide if the symbols matching __cxx11 or B5cxx11 are part of the<br>
library API, and are used by the reverse dependencies of the<br>
library.<br>
<br>
- If there are no symbols matching __cxx11 or B5cxx11 in the symbols<br>
forming the library API, you should close this issue with a short<br>
explanation.<br>
<br>
- If there are no reverse dependencies, it should be the package<br>
maintainers decision if a transition is needed. However this might<br>
break software which is not in the Debian archive, and built<br>
against these packages.<br>
<br>
- If a library transition is needed, please prepare for the change.<br>
Rename the library package, append "v5" to the name of the package<br>
(e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you<br>
have a soversion bump and you upload this version instead of the<br>
renamed package. Prepare a patch and attach it to this issue (mark<br>
this issue with patch), so that it is possible to NMU such a<br>
package. We'll probably have more than hundred transitions<br>
triggered. Then reassign the issue to <a href="http://release.debian.org" rel="noreferrer" target="_blank">release.debian.org</a> and<br>
properly tag it as a transition issue, by sending an email to<br>
<a href="mailto:control@bugs.debian.org">control@bugs.debian.org</a>:<br>
<br>
user <a href="mailto:release.debian.org@packages.debian.org">release.debian.org@packages.debian.org</a><br>
usertag <this issue> + transition<br>
block <this issue> by 790756<br>
reassign <this issue> <a href="http://release.debian.org" rel="noreferrer" target="_blank">release.debian.org</a><br>
<br>
- If unsure if a transition is needed, please tag the issue with help<br>
to ask for feedback from other Debian developers.<br>
<br>
The libstdc++6 transition will be a large one, and it will come with a<br>
lot of pain. Please help it by preparing the follow-up transitions.<br>
<br>
[1] <a href="https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition" rel="noreferrer" target="_blank">https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition</a><br>
<br>_______________________________________________<br>
Pkg-crosswire-devel mailing list<br>
<a href="mailto:Pkg-crosswire-devel@lists.alioth.debian.org">Pkg-crosswire-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel</a><br></blockquote></div><br></div></div></div></div></div>