Processed: Re: Bug#798008: yaml-cpp: library transition needed with GCC 5 as default

[Debian Bug Tracking System]

Processing control commands:

> tags 798008 + patch pending
Bug #798008 [src:yaml-cpp] yaml-cpp: library transition needed with GCC 5 as 
default
Added tag(s) pending and patch.

-- 
798008: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#798008: yaml-cpp: library transition needed with GCC 5 as default

[Simon McVittie]

Control: tags 798008 + patch pending

On Fri, 04 Sep 2015 at 14:18:50 +0200, Julien Cristau wrote:
>Then reassign the issue to release.debian.org and
>properly tag it as a transition issue

This was already done,  (but I thought
you'd stopped wanting people to do this and started wanting people to
just upload and close the bug in any case).

There's a patch from a maintainer on that bug, which I have built locally
and build-tested with librime. It's ready for sponsored upload, unless you
want me to hold off because of the previous ABI break in
.

Please let me know whether I should upload or do something else.

S

Bug#798008: yaml-cpp: library transition needed with GCC 5 as default

[Julien Cristau]

Source: yaml-cpp
Version: 0.5.2-1
Severity: serious
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Hi,

your library exposes std::string or std::list in its public API, and
therefore the library package 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 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. 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
   cont...@bugs.debian.org:
   
 user release.debian@packages.debian.org
 usertag  + transition
 block  by 790756
 reassign  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



signature.asc
Description: Digital signature