[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#791268: marked as done (rlog: library transition may be needed when GCC 5 is the default)

Your message dated Tue, 04 Aug 2015 10:00:39 +0000
with message-id <E1ZMZ1T-0006VC-Os@franck.debian.org>
and subject line Bug#791268: fixed in rlog 1.4-4
has caused the Debian Bug report #791268,
regarding rlog: library transition may be needed when GCC 5 is the default
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 owner@bugs.debian.org
immediately.)


-- 
791268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791268
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:rlog
Version: 1.4-2.1
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 --- 
Source: rlog
Source-Version: 1.4-4

We believe that the bug you reported is fixed in the latest version of
rlog, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 791268@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Eduard Bloch <blade@debian.org> (supplier of updated rlog package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 03 Aug 2015 20:07:54 +0200
Source: rlog
Binary: librlog-dev librlog5v5
Architecture: source amd64
Version: 1.4-4
Distribution: unstable
Urgency: medium
Maintainer: Eduard Bloch <blade@debian.org>
Changed-By: Eduard Bloch <blade@debian.org>
Description:
 librlog-dev - flexible message logging library - development files
 librlog5v5 - flexible message logging library
Closes: 791268
Changes:
 rlog (1.4-4) unstable; urgency=medium
 .
   * GCC5 transition (librlog5 -> librlog5v5, closes: #791268)
Checksums-Sha1:
 3b10be834f246f919c2e8a3402547723cb90f717 1702 rlog_1.4-4.dsc
 e5f44fea7fe8b0f292a982a124af49b3a01ce0a3 2740 rlog_1.4-4.debian.tar.xz
 d1c8538b71e68f5d969641ca6f2fb09fd744a5eb 251164 librlog-dev_1.4-4_amd64.deb
 f349b9e2d1c45a07e0e500016171f86d51975bf2 22116 librlog5v5_1.4-4_amd64.deb
Checksums-Sha256:
 6ef85529667318bf0ab891e6b7dfc062a8500130f29d5fd2589740aa1632b187 1702 rlog_1.4-4.dsc
 bbf29b12fc126b646f575377996004b5de7a0daf18f6ed6eca667e204d5ec1dd 2740 rlog_1.4-4.debian.tar.xz
 3d786826059e0514325c1098dadaede28114a000af9719459370a19aae96b07d 251164 librlog-dev_1.4-4_amd64.deb
 f5dc151a0e7b7d709f00ec747ba322bab26239be8a636d73cd86ea3686b1f7f8 22116 librlog5v5_1.4-4_amd64.deb
Files:
 e874b03362522314d585eefbfd63efe2 1702 libs optional rlog_1.4-4.dsc
 d161001d1b1b3eedc4e552a4cf734bde 2740 libs optional rlog_1.4-4.debian.tar.xz
 4b9cb472309a13c23e414e53a606e54b 251164 libdevel optional librlog-dev_1.4-4_amd64.deb
 cc1eb5a10c27ff26598d4ce50fcbbf9b 22116 libs optional librlog5v5_1.4-4_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIVAwUBVb+wNWl0DlyzX+w8AQhmww/9FjgCuceWw1WH430dE91HFMO1m10WrIK7
HO5H7eECUx3vMisl4KESz1Nky38Spfde1Bfbe5hw+2ibTOYFoJfMu1xENkro2iyy
8uLoqhjaZATJnKhGS9hKd7B37fQjWcT6tj6pkKH1wYxiqKeqc+wZ+whkGSM3azR2
t0BzEg/qKt+Wa9zQKUtGlP9EXM7iizpcUSyfr2KPTJruW9cPSp2bqxmgTe8P6CSC
LgRMb1IkKzSXnVaBPsSQRQnCtr9IvneIPo/iaBAaZwrF/LyPZAjX3wy1rkgUOfC7
bjLpa80MLC/ubJcw/TdNkTbBs2N+HlP0yPH8izDy2znxcHu5gVH7y+UEKPJxFeq8
Rt3hHI3Lx267bwWZVgrXTBJjSydesCqz6aKGnr9HXMSyXohSBC41qM3jW3Jo7nSw
sfBbuo5+YTVj3UIDlFOtlPx4Zl9Amc/zgpvLrb3lGVGaTGnwB0c7FqfEMFdn+5Hu
XQOOzcEjCjk0iHSbyQ2jJqCHbjHAac6HLO8xu65BF+CBq3g3ou2B+Ll0CUHwcNYE
/sulL22vJ5PxkECzMXx7LFI0KUPcwS5ooNV/c122knRzJJPB3+DlIwsIdMgW9NAq
kaR470GLNOKC4FiLt25+2XN6Y+ntjfiL3WkwHoED3Iys6FisMVbDv/pi5Y9npwX3
ANKOO5Ljxn0=
=uHiA
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: