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

Bug#796721: marked as done (tntnet: library transition needed with GCC 5 as default)

Your message dated Mon, 26 Oct 2015 11:00:27 +0000
with message-id <E1ZqfVr-0000Ir-N3@franck.debian.org>
and subject line Bug#796721: fixed in tntnet 2.2.1-2
has caused the Debian Bug report #796721,
regarding tntnet: library transition needed with GCC 5 as 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.)


-- 
796721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796721
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: tntnet
Version: 2.2.1-1
Tags: sid stretch
User: debian-gcc@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
   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

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
Source: tntnet
Source-Version: 2.2.1-2

We believe that the bug you reported is fixed in the latest version of
tntnet, 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 796721@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kari Pahula <kaol@debian.org> (supplier of updated tntnet 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: Sat, 05 Sep 2015 18:57:54 +0300
Source: tntnet
Binary: tntnet tntnet-doc tntnet-demos libtntnet12v5 libtntnet-dev tntnet-runtime
Architecture: source amd64 all
Version: 2.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Kari Pahula <kaol@debian.org>
Changed-By: Kari Pahula <kaol@debian.org>
Description:
 libtntnet-dev - Tntnet library development headers
 libtntnet12v5 - Tntnet libraries
 tntnet     - modular, multithreaded web application server for C++
 tntnet-demos - demo web applications for Tntnet
 tntnet-doc - documentation for Tntnet
 tntnet-runtime - Tntnet runtime system
Closes: 796721
Changes:
 tntnet (2.2.1-2) unstable; urgency=medium
 .
   * Bump library package name to 12v5 for C++ ABI transition.  (Closes:
     #796721)
   * Bump Standards-Version to 3.9.6 (No changes necessary)
Checksums-Sha1:
 7193bd5a18be1743340fa44fe5f0fcdc1ebf45ad 2035 tntnet_2.2.1-2.dsc
 108b8165e8b251a877b929f0cb58d0edb2ca4eb7 41392 tntnet_2.2.1-2.debian.tar.xz
 ee2323e6f77d6fb15d9144f6a3776083159ae364 129242 libtntnet-dev_2.2.1-2_amd64.deb
 daa0e0b410023787548be6d165a2ebd52762d4f1 260248 libtntnet12v5_2.2.1-2_amd64.deb
 c35c067c674e7fa0be6261c25d16532a414c4f22 253338 tntnet-demos_2.2.1-2_amd64.deb
 c7f7cdca7775823b66354499af4261b48f4f6110 474692 tntnet-doc_2.2.1-2_all.deb
 1b72be1327367a8a112ab3868e6463a151c7cfe5 62930 tntnet-runtime_2.2.1-2_amd64.deb
 a0aba67ddbeafaf904d5fd8f6a2f9ae01c957119 68546 tntnet_2.2.1-2_amd64.deb
Checksums-Sha256:
 90b331eddc4cee09b53e9c089cc9de4b24e6b5ecdbc53456d684d8aa4cf10934 2035 tntnet_2.2.1-2.dsc
 69f9940757a2a85a83cee8d9110a7dc59a52d81cf77fb6a73b6c22feab32141e 41392 tntnet_2.2.1-2.debian.tar.xz
 ad2b00e0a669a4cb77515f28a63a35b1d99e6739d385aa024d9ce30bf703241a 129242 libtntnet-dev_2.2.1-2_amd64.deb
 c6e8d0faad358f2276c8688cd45eb4c77baf80f036a1ad00266c45360b0b97cf 260248 libtntnet12v5_2.2.1-2_amd64.deb
 ff85fc1de4436a85f6f79766ef7606d6d8bf4b52cf0232bce827cff04bfa7748 253338 tntnet-demos_2.2.1-2_amd64.deb
 44f44fd345db4a4ac0545ebb7b7069c6b99cfe4c7ca9e260c88c5bac4d7a1dd7 474692 tntnet-doc_2.2.1-2_all.deb
 21bab70cea3cde746a7f9b7f721476b1017ac7a56b07f2b198ba7c998dbfd4d6 62930 tntnet-runtime_2.2.1-2_amd64.deb
 851cabb4f33f31e0fb6fcc731eb3d70b981084b1596856f2d516e604aae8112f 68546 tntnet_2.2.1-2_amd64.deb
Files:
 287906ea5c1f9b15b9e54871eefe933f 2035 httpd extra tntnet_2.2.1-2.dsc
 c5ab5e68e944b27fd96c07d404fa8bdf 41392 httpd extra tntnet_2.2.1-2.debian.tar.xz
 b4810de6e11708f277b0c81fc7bd2f52 129242 libdevel extra libtntnet-dev_2.2.1-2_amd64.deb
 6ae4859a8bdabcd7f74ceb0de548ff3f 260248 libs extra libtntnet12v5_2.2.1-2_amd64.deb
 5c2558da8448bb7f14ce6da3ddf31e5b 253338 doc extra tntnet-demos_2.2.1-2_amd64.deb
 6ed6f411a7935c60c59c326b346e61f9 474692 doc extra tntnet-doc_2.2.1-2_all.deb
 918da4354a684ddcf66349e171d16aa3 62930 httpd extra tntnet-runtime_2.2.1-2_amd64.deb
 a21a8e12849ae5d759dd2d867a472fd6 68546 httpd extra tntnet_2.2.1-2_amd64.deb

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

iQIcBAEBCAAGBQJWLIa9AAoJEIQIZ+6djyZcwJ8QALpFLkxt+T5mat+oCYekC9Mm
ham1M3sJ9BfyuJd4H70pfWB0VzpN+0mwzMHLHzXEtQnr80lOYeOLfo72m4isWXn5
B32x17EXO1Fh7IZui6WkfhTUJSzIqzizbD+h8qySYTfR8+pnSG9KNZHYYgM1AY38
GKU8XDEwRHW4qfs8byyxmcqRM3Gkld8wFKN1clbNuh7r+rzcEASC24LmQKJ/Cb0x
ZlBMJciMOBhYztr/nOYqHco6bLTAqmOmHNH7mYbw21HZvoAeDTdKmbF74KCzKdnw
LsrgR2+13KPlB0ePPpL32L3RfxRSub6QhZEz8JIDmj995mAD3NwPrXaE3qzPoAis
8EKKAIhBgMIRBCEMNnD19MuxyOcEE/oEeanHgYUdzHm1jGrR9IAFDBbGXD4QhBAG
4yeza82IV2DMK3PX174CGdyVpBmytX5yOILEeEFXMXdHGwP4azYwIWtgGLd2H7q0
8IG3lHroxTfZQn2Ubxw6g294mYikcr9YkanSO8mFk8GyTVj+Vkh/AtDooPhTTm6r
TW9db51dsyXfSPIFWfPzO3znCsLtrexr7r3o3J0IXeT9YUmNWgBwHG6l8dCm89M/
6VVfWPb4DD93H6IMaOxTFi0j6J3baCxZk6nWfFC7p3Z6Wg+jdlkSZTW9Md47oSLq
U/izWy82L41IcDwiyKPR
=olZ3
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: