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

Bug#796719: marked as done (tntdb: library transition needed with GCC 5 as default)

Your message dated Mon, 26 Oct 2015 11:00:26 +0000
with message-id <E1ZqfVq-0000IW-92@franck.debian.org>
and subject line Bug#796719: fixed in tntdb 1.3-3
has caused the Debian Bug report #796719,
regarding tntdb: 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.)


-- 
796719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796719
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: tntdb
Version: 1.3-2
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: tntdb
Source-Version: 1.3-3

We believe that the bug you reported is fixed in the latest version of
tntdb, 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 796719@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 tntdb 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 20:44:44 +0300
Source: tntdb
Binary: libtntdb4v5 tntdb-mysql4v5 tntdb-postgresql4v5 tntdb-sqlite4v5 libtntdb-dev
Architecture: source amd64
Version: 1.3-3
Distribution: unstable
Urgency: medium
Maintainer: Kari Pahula <kaol@debian.org>
Changed-By: Kari Pahula <kaol@debian.org>
Description:
 libtntdb-dev - Development headers for tntdb
 libtntdb4v5 - C++ class library for easy database access
 tntdb-mysql4v5 - MySQL backend for tntdb database access library
 tntdb-postgresql4v5 - PostgreSQL backend for tntdb database access library
 tntdb-sqlite4v5 - SQLite backend for tntdb database access library
Closes: 796719
Changes:
 tntdb (1.3-3) unstable; urgency=medium
 .
   * Bump library package names to 4v5 for C++ ABI transition.  (Closes:
     #796719)
   * Bump Standards-Version to 3.9.6 (No changes necessary)
Checksums-Sha1:
 a60ad1a15c1d5d6a8edbb60b5a56a18389c6d247 2075 tntdb_1.3-3.dsc
 1d1f0b076d6b906108c02632a3575745c94a65b2 3684 tntdb_1.3-3.debian.tar.xz
 d758476969e67893b6c363f64ce47ba359dbce46 244452 libtntdb-dev_1.3-3_amd64.deb
 b12cdd5b7bde711b46ddcd4200e282db85fb9e0d 97464 libtntdb4v5_1.3-3_amd64.deb
 986b0d572f3d1b4bc7ce570349648dff926a5d8a 75198 tntdb-mysql4v5_1.3-3_amd64.deb
 3e1b228a62247a987543f61a1de812deac1871e5 69720 tntdb-postgresql4v5_1.3-3_amd64.deb
 e1c399b81ebb8315e3af3b7bf5e445c5b2607a28 53844 tntdb-sqlite4v5_1.3-3_amd64.deb
Checksums-Sha256:
 28a0ae6d0d51d1274ec1c2e2ed29f8ccbe4157cf8916898768bdabc5eaa4e66b 2075 tntdb_1.3-3.dsc
 6f9994975f064c7bf2db423e1fc09b7e7965abe38a941c8c6330808cbfbdc8ac 3684 tntdb_1.3-3.debian.tar.xz
 b8229e7815e42ab0b0e92dee45b2671a7cc5d703f85ed6c24399ad811cfd5145 244452 libtntdb-dev_1.3-3_amd64.deb
 54b02c7fad6b749afcc4f8dc44a0d1d692a84e3ec9a637bf7e3ab2b05a316048 97464 libtntdb4v5_1.3-3_amd64.deb
 9f13cbd93fadab3955906abd46a006819b00b3bfc9c3c9d9910cb5021e7aff70 75198 tntdb-mysql4v5_1.3-3_amd64.deb
 a0eaccb47bbda0657a5b4172eb6b75d611d1be7ec1b89aa2afc9a749e156f3c9 69720 tntdb-postgresql4v5_1.3-3_amd64.deb
 20b86d056cc3be56ec9bbc324ef7c75ea196dd86ab5f8d320a5b4e58f97051de 53844 tntdb-sqlite4v5_1.3-3_amd64.deb
Files:
 f1d7107f21b2e62e47013c8aec2a991e 2075 libs optional tntdb_1.3-3.dsc
 ba7411d4673bb1dc9be3681e0d7a41d4 3684 libs optional tntdb_1.3-3.debian.tar.xz
 6606a7a85076f8cb00023bf8a208129a 244452 libdevel optional libtntdb-dev_1.3-3_amd64.deb
 835736ea8274b5ea0aae1de85ef9072c 97464 libs optional libtntdb4v5_1.3-3_amd64.deb
 e9ee28895be80fa657580313f0c47dac 75198 libs optional tntdb-mysql4v5_1.3-3_amd64.deb
 cc4d856f176797d8149e998b5b3ab665 69720 libs optional tntdb-postgresql4v5_1.3-3_amd64.deb
 2771a5fda3beb978413bc3361ea6316c 53844 libs optional tntdb-sqlite4v5_1.3-3_amd64.deb

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

iQIcBAEBCAAGBQJWLIfmAAoJEIQIZ+6djyZcmdEQAMXuKDs4KchhrG0hrdvFasaH
2r0jzTqTRfnkV44FwSwDvitArz619kzn8ObtS9xGb4rxKL8PhkMmxwpPT7TbdSvG
Y1eW/XCD0IHA8JAHoquKoajeGQFH+gNFKcO20s5ba6Y0+BoRh1vccnSMeSTj1Rt+
rpPyFIwcRCjgsMAn3XFYRY2JNvgYgNC6NWom6mN35QJ5WEMBAKvm0NJRzq8wqC/L
+bmqhCdDRZcTQCZBB67PlNmWFSE/gori5+DrjObv+T315o5IK/TUJ+oowJJyPgh7
wCTFMNbOxKuQ/5X/IWO03zANtpeKf3pYEMcKe2l5sfUFKJoZyEHw+9mWs5kh8J8n
V4pPSiDhNrrIb5xhkDqHkSq5MW9vEKXet3j8PISbv5Z+cu9wVosMSnS62IN4+6ub
7TWYhHb9t8t9xcCLGQ+3mz1D9vhwN24BordqhQt5PazoquU53sqPCcruBD4dqWJJ
7YyJyZ7Ar6FlBeyT8pwZmalCTQf5nbmsE/LpcHoFYmMBQWw0JgWRJCO7ft3lCwHt
WqnHQMRSZvrl0iN9OwH61lwc2eonOaX1wkNJIIVi4tTe9XFErCGen9j7qbN3fNQd
OAltusQQecmELwYwhqdRII01s0/vqQ3kna0/+cqs9RSWSnofDp6/mzUCPFt4NkLZ
bB7JA9+Oly+tvEpJwNpe
=tyI1
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: