Your message dated Mon, 23 Nov 2015 12:03:24 +0100
with message-id <20151123110324.ga6...@enricozini.org>
and subject line Version 3.3 has been uploaded
has caused the Debian Bug report #798703,
regarding wreport: ABI transition needed for libstdc++ v5
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
798703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wreport
Version: 2.14-1
Severity: serious
Justification: breaks ABI without a package rename
Tags: sid stretch
User: debian-...@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,
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.
In the case of wreport, std::string appears in functions in public
headers (for example Var::format), so it seems very likely that a
transition is needed. The transition normally consists of renaming the
affected library packages, adding a v5 suffix (libwreport2v5).
The SONAME should not be changed when doing this.
If an upgrade to a new upstream SONAME is already planned, and that
SONAME has never been available in Debian compiled with g++-4, then an
alternative way to carry out the transition would be to bump the
SONAME.
These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.
Looking at the build-dependencies of wreport, the only C++ library
seems to be libwibble, which is static (and was already rebuilt).
So this sub-transition is ready to start.
The package might be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.
Regards,
S
[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg00000.html
--- End Message ---
--- Begin Message ---
Hello,
version 3.3 of wreport has been uploaded, and it has built with gcc5: it
looks like these bugs can be closed now.
Enrico
--
GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <enr...@enricozini.org>
signature.asc
Description: PGP signature
--- End Message ---
