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

Bug#796711: marked as done (sword: library transition is needed with GCC 5 as default)

Your message dated Tue, 15 Sep 2015 10:00:30 +0000
with message-id <E1Zbn2M-0006iZ-0q@franck.debian.org>
and subject line Bug#796711: fixed in sword 1.7.3+dfsg-5
has caused the Debian Bug report #796711,
regarding sword: library transition is 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.)


-- 
796711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796711
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: sword
Version: 1.7.3+dfsg-2.1
Severity: serious
Tags: sid stretch
User: debian-gcc@lists.debian.org
Usertags: libstdc++-cxx11

Hi,

sword's public API relies on types like std::string and std::list
provided by libstdc++6, meaning that libsword11 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 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-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: sword
Source-Version: 1.7.3+dfsg-5

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

Debian distribution maintenance software
pp.
Daniel Glassey <wdg@debian.org> (supplier of updated sword 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, 14 Sep 2015 11:45:04 +0100
Source: sword
Binary: libsword11v5 libsword-dev libsword-common libsword-utils libsword-dbg diatheke
Architecture: source amd64 all
Version: 1.7.3+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: CrossWire Packages <pkg-crosswire-devel@lists.alioth.debian.org>
Changed-By: Daniel Glassey <wdg@debian.org>
Description:
 diatheke   - command line bible browsing and search tool
 libsword-common - common settings and module repository for libsword
 libsword-dbg - API/library for bible software - Debug Files
 libsword-dev - Development files for libsword
 libsword-utils - conversion utilities for bible documents in SWORD supported forma
 libsword11v5 - API/library for bible software
Closes: 696742 796711
Changes:
 sword (1.7.3+dfsg-5) unstable; urgency=medium
 .
   * Rebuild with correct orig.tar.gz
   * c++ transition, Closes: #796711
   * debian/control:
       diatheke provides sword-frontend, Closes: #696742
Checksums-Sha1:
 c32ba3931d77de4eea37ca946989b6b5e6960736 2264 sword_1.7.3+dfsg-5.dsc
 b975b921dec9f9103af395c153522cf1c26d719e 24452 sword_1.7.3+dfsg-5.debian.tar.xz
 780c2f933b3e8196c1516fe545ff9b27c289cff6 82046 diatheke_1.7.3+dfsg-5_amd64.deb
 ca85804070c1ad7b32499b4816923c077f247199 143374 libsword-common_1.7.3+dfsg-5_all.deb
 3d5f99fc942a3c2ff248222ece232ec85653660a 4113198 libsword-dbg_1.7.3+dfsg-5_amd64.deb
 c1abc16dfb0d75029ba89f9c2c268aad9950fb5e 610218 libsword-dev_1.7.3+dfsg-5_amd64.deb
 1080eae4c1842b373178c82554ad05e286b9157f 149642 libsword-utils_1.7.3+dfsg-5_amd64.deb
 ecdab77cb043061e6b50d0b0aa58963526178890 454882 libsword11v5_1.7.3+dfsg-5_amd64.deb
Checksums-Sha256:
 b2952dd1cd7f7e5a51e3a98518bdf8b78abeadeee0c6d82b2ed484eef2c822a8 2264 sword_1.7.3+dfsg-5.dsc
 f5f37567e24b17f497b1898a421e33a1e1e6a91ab25e674252554a463b9fd5b9 24452 sword_1.7.3+dfsg-5.debian.tar.xz
 f458bb3f064d9c12f018256990b518319b0d18fccd96723fe3518deff4e5f3a0 82046 diatheke_1.7.3+dfsg-5_amd64.deb
 c38724f67c6306410ca93190c0746668b937151e3115d3ed22ae62db421f1795 143374 libsword-common_1.7.3+dfsg-5_all.deb
 78451ed59884c7ff405c23038394c70f30e623d239b535e612b9e429ee89846d 4113198 libsword-dbg_1.7.3+dfsg-5_amd64.deb
 a88e3d7d6b0954b7eadf965feb04028c9901ebf508bfa5cb0eda640ba3421c93 610218 libsword-dev_1.7.3+dfsg-5_amd64.deb
 21bec2d4f1d42f485d807ab29aad4b5a652ab71c4997fe022796d1d519d8442d 149642 libsword-utils_1.7.3+dfsg-5_amd64.deb
 d0c5498c14d70eb258357d6a143530b15c1ea4e1a633f78869be269622f31b83 454882 libsword11v5_1.7.3+dfsg-5_amd64.deb
Files:
 4b585e59d3eecf13a70b4ff738abe8aa 2264 libs optional sword_1.7.3+dfsg-5.dsc
 9faace242feda3eef837236b345127cf 24452 libs optional sword_1.7.3+dfsg-5.debian.tar.xz
 5660581b4f574cf5417a7d4f6831165b 82046 text optional diatheke_1.7.3+dfsg-5_amd64.deb
 d58401690f302583b80fa3c63644303b 143374 devel optional libsword-common_1.7.3+dfsg-5_all.deb
 f234574e13c0348ab30167ade163e11e 4113198 debug extra libsword-dbg_1.7.3+dfsg-5_amd64.deb
 8ebc0475aaba0c90d831b4dde2993bb4 610218 libdevel optional libsword-dev_1.7.3+dfsg-5_amd64.deb
 5aba056d347fabed2d15b2712ad3361a 149642 devel optional libsword-utils_1.7.3+dfsg-5_amd64.deb
 c07ef7345b85ad63af8391f5a7275681 454882 libs optional libsword11v5_1.7.3+dfsg-5_amd64.deb

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

iQIcBAEBCAAGBQJV9rJHAAoJEASbEDOvBgxa1fwP/ioZQ5u9VhqxvyKh9sf5wxXl
8vwTgkK7TD56ocKM80TUfITzuTwm61zhgAJQzRZkpZE4I+QoORyIAcBxVx6fC9Gk
EYh8aTDiFFxI9Xd6FLztUZ9yuxgH5eQl753cSdCDJVj7guxeaO4hfiu0ouSrUyjq
FW4VWf4qkFJEb37lbSRAYFyjbXXrpevahzEwOugi9p2MsXQ1KNaUXHg2JvruTxMg
PWIh2yW7z2w7FODuROR+88pKE/+QRtoUIB3B9990eeD+l+4f8ywVWiEAaFUl8r0F
SiLVEprnDofcM/9z20or0s4dvo3Vzr2AcpvIKCx2EURnhf3JMlSsT/0+7AddybaO
A1l13okO8iq2R7r0+wB1S7PxNAGfhuDNSxeW8IDjGB45HtNNMrmVKojw4z7J3onK
ds8RPmJJ9G8rlVoNTTXs+PcRvQ8J+6/Zloh23391EwQqb6Kp3OpFlWcrtqrwy231
z8BcfWVjc1uJHteCYM8bZt8OEdu/eMLCQChPfrlog1kfkzV1mD+uGs2EVzGutWlQ
WnrD4ophuQn6/wdmLlkIEI7lQ/GVh9oHWgotcfHmyUEf9vtbCYV6anQsviyvDZxc
zWIK5JCf/ADnTa+2WFAYBekiBrIerhSqB/FS0SyCnPKxdBbKuQGU+0J3w02/KvCc
fEjZS3yl2n1p36PKnx5K
=Bs24
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: