From doko at debian.org  Fri Jul  3 13:11:37 2015
From: doko at debian.org (Matthias Klose)
Date: Fri, 03 Jul 2015 13:11:37 +0000
Subject: [pkg-kolab] Bug#791133: libkolabxml: library transition may be
	needed when GCC 5 is the default
Message-ID: <E1ZB0kj-0007GL-CW@paradis.debian.org>

Package: src:libkolabxml
Version: 1.1.0-3
Severity: important
Tags: sid stretch
User: debian-gcc at 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,
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-20150701/
   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


From doko at debian.org  Wed Jul 22 13:33:42 2015
From: doko at debian.org (Matthias Klose)
Date: Wed, 22 Jul 2015 13:33:42 +0000
Subject: [pkg-kolab] Bug#793252: libkolabxml: change of type in system_error
	might break with GCC-5
Message-ID: <E1ZHu9W-0000D1-KR@paradis.debian.org>

Package: src:libkolabxml
Severity: important
Tags: sid stretch
User: debian-gcc at lists.debian.org
Usertags: gcc-pr66145

GCC PR libstdc++/66145 is a regression in GCC 5 which won't be fixed
upstream in time for the GCC defaults change.  The work around is to
rebuild the affected packages after GCC 5 is the default compiler.
Please look at the code and decide, if the package is affected. If
not, please just close the issue.  If it's a real issue, I'll add
the packages affected to libstdc++6's Breaks attributes, with the
version of the package at the time of the defaults change.

See https://wiki.debian.org/GCC5#libstdc.2B-.2B-_c.2B-.2B-11_incompatibilities_.284.9_and_5.29
for further information.

To build with GCC 5,install the gcc, g++, gfortran, ... packages
from experimental (apt-get -t experimental install g++).