--- Begin Message ---
- To: maintonly@bugs.debian.org
- Subject: verbiste: library transition may be needed when GCC 5 is the default
- From: Matthias Klose <doko@debian.org>
- Date: Fri, 03 Jul 2015 13:14:49 +0000
- Message-id: <E1ZB0np-0007xe-Uz@paradis.debian.org>
Package: src:verbiste
Version: 0.1.41-4
Severity: important
Tags: sid stretch
User: debian-gcc@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@bugs.debian.org:
user release.debian.org@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
--- End Message ---
--- Begin Message ---
- To: 791329-done@bugs.debian.org
- Subject: Re: Reopening
- From: Emilio Pozuelo Monfort <pochu@debian.org>
- Date: Sat, 26 Sep 2015 14:52:25 +0200
- Message-id: <56069509.9080604@debian.org>
- In-reply-to: <20150805081555.GA6955@buchert.pl>
- References: <20150805081555.GA6955@buchert.pl> <20150805081555.GA6955@buchert.pl>
On Wed, 5 Aug 2015 10:15:55 +0200 Tomasz Buchert <tomasz@debian.org> wrote:
> Hi,
> I reopened this issue, although I've uploaded a version with ABI change.
> It seems that I shouldn't close it, as it was the case here:
> https://bugs.debian.org/791131
>
> It's my first transition, so I'm not sure how it works.
This is now over. closing.
Emilio
--- End Message ---