Your message dated Wed, 29 Jul 2015 18:00:22 +0000
with message-id <[email protected]>
and subject line Bug#791312: fixed in xapian-core 1.2.21-1.1
has caused the Debian Bug report #791312,
regarding xapian-core: 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 [email protected]
immediately.)


-- 
791312: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791312
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:xapian-core
Version: 1.2.21-1
Severity: important
Tags: sid stretch
User: [email protected]
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
   [email protected]:
   
     user [email protected]
     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: xapian-core
Source-Version: 1.2.21-1.1

We believe that the bug you reported is fixed in the latest version of
xapian-core, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose <[email protected]> (supplier of updated xapian-core 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 [email protected])


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

Format: 1.8
Date: Tue, 28 Jul 2015 20:58:38 +0200
Source: xapian-core
Binary: libxapian22v5 libxapian22v5-dbg libxapian-dev xapian-tools xapian-doc 
xapian-examples
Architecture: source amd64 all
Version: 1.2.21-1.1
Distribution: experimental
Urgency: medium
Maintainer: Olly Betts <[email protected]>
Changed-By: Matthias Klose <[email protected]>
Description:
 libxapian-dev - Development files for Xapian search engine library
 libxapian22v5 - Search engine library
 libxapian22v5-dbg - Debugging symbols for the Xapian Search engine library
 xapian-doc - Core Xapian documentation
 xapian-examples - Xapian simple example programs
 xapian-tools - Basic tools for Xapian search engine library
Closes: 791312
Changes:
 xapian-core (1.2.21-1.1) experimental; urgency=medium
 .
   * Non maintainer upload.
   * Build using GCC 5. Closes: #791312.
   * Rename libxapian22-dbg to libxapian22v5-dbg.
   * Rename libxapian22 to libxapian22v5.
   * Add Conflict/Replaces.
Checksums-Sha1:
 09d0668f529e393f4e9267adad3bd8ff133a9853 2229 xapian-core_1.2.21-1.1.dsc
 1c36a8a677f0eda5ed084837288d9e8c48f33236 16612 
xapian-core_1.2.21-1.1.debian.tar.xz
 eb521034152fa769b220906412ab79a51d5a7df6 1172594 
libxapian-dev_1.2.21-1.1_amd64.deb
 2807b07edd6c7dc551c99af33e3866dac61a938a 5964394 
libxapian22v5-dbg_1.2.21-1.1_amd64.deb
 71bd4fc0513047fe50bd71f54089b16c6927cc2a 972692 
libxapian22v5_1.2.21-1.1_amd64.deb
 c363ebe4297a0553992d0fb4b244c7bbf98e108f 2048572 xapian-doc_1.2.21-1.1_all.deb
 c14a48beec2425a665dbce6efa12ed2d66b4aded 410814 
xapian-examples_1.2.21-1.1_amd64.deb
 ec092bc54d60149905a578a9e75b9146230c24c2 473762 
xapian-tools_1.2.21-1.1_amd64.deb
Checksums-Sha256:
 e333453ed091d7e61fd1fb7d90940ebf0ad01e4d08051c825bf5a6026f1ba55a 2229 
xapian-core_1.2.21-1.1.dsc
 bee0690a8df6c00942625283e8c0a6303d24c747a5a79162224141f9e06bb222 16612 
xapian-core_1.2.21-1.1.debian.tar.xz
 e684a7e08f862dc896503caabebf0730e4144289971268c6aaaa7cce5c93f127 1172594 
libxapian-dev_1.2.21-1.1_amd64.deb
 bc7c60b429e09337e2448eaf50a6589cdc02375639a833346cc165b435cf8481 5964394 
libxapian22v5-dbg_1.2.21-1.1_amd64.deb
 d1f789bdfef6ffcf3bc695a6058f1cac498e5920a361782800b04ba6975ce680 972692 
libxapian22v5_1.2.21-1.1_amd64.deb
 ece21f64329009e563cf2a8708e37e6a6f35cee64a76b5b508593ecfb3aecbb8 2048572 
xapian-doc_1.2.21-1.1_all.deb
 e3bc12ccb55096d72b4ebb2a99fa2cbbfb99494ca2a766c51cc4d769c5d36f70 410814 
xapian-examples_1.2.21-1.1_amd64.deb
 d7dca979985d85d8a899e04146c0b5f60620c4fc159ea50e487d7481a1658d06 473762 
xapian-tools_1.2.21-1.1_amd64.deb
Files:
 9c1703c188b2ae9bec7b05f5dcfa9645 2229 libs important xapian-core_1.2.21-1.1.dsc
 032bc132e5b6b46c7da43664e921fe2b 16612 libs important 
xapian-core_1.2.21-1.1.debian.tar.xz
 b9151067cb7e5c03ac81a24b7e00f058 1172594 libdevel optional 
libxapian-dev_1.2.21-1.1_amd64.deb
 280b9ed6e94ca500393d677d158b00e2 5964394 debug extra 
libxapian22v5-dbg_1.2.21-1.1_amd64.deb
 c65cee4a7162983ff747b0d2153578b7 972692 libs important 
libxapian22v5_1.2.21-1.1_amd64.deb
 ead8471d83bd379fb20ba855dcff18a6 2048572 doc optional 
xapian-doc_1.2.21-1.1_all.deb
 b36848d4b0e30c10d2d7f73157686942 410814 doc optional 
xapian-examples_1.2.21-1.1_amd64.deb
 dba44389ea3444cb78031c7bcb2ced88 473762 utils optional 
xapian-tools_1.2.21-1.1_amd64.deb

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

iQIcBAEBCAAGBQJVuNhUAAoJEL1+qmB3j6b1bXUP/A33g0SXvSKNnQI59HbdIF1c
gQcmYQsihaXI5BSUv7+0X8U05Dqb84Ljc1a/OmaEr2fJqEkAusS7IC92r6NM5FmG
hvT5PNJ0iIZz4kczF8ZKBiPVeUPgIGaAUNRDvl0JC36k3dbwZPqhmdVTHOM62V9f
y1uOw+zxyfd2ASQlKLZnJEgOqAJJj9ysOfWSVTmOeYS25DBerrwJobC2Ao9qTsi/
pebOhiZX6GKOk2z3fmtryoUXdpKjkmLDXUTn4GDIPeRpDglTcVx/qhOC8jNMfcKc
kAivJYOSq5TNqzvcvmzL3UJQMExzbHLrSFkEVH4Y2TiKDJoNNfMiVwGmgl4w8XYk
hXtNlQBK9arjLauhMlmXdNo1sNDdRi18idNLMqFwlqzqzRmVE5ZXOva8p0su0ekN
yz1zrspgltNXePe/IM+O8APFcP3E7MX+xBDznbkZcXR0OewX55ONnAhrtG8XL8Cp
oBwyLvBuFDWI7/CkNfHmSJZVsz2X7vnqLdn75v4uyjO+EDKVHBQ0ttvzcWUuPvI3
vihUBBUVGPnpFD7KlyH5sJX64IkkWJEUeDKvvQY3cFndtMV+SHWQ6CPzdvyuNjVg
r1wPcha/Ajdd1nCdScKxXUZ4dWi4lOE2PW8QidNe0VDpMP2KOuk+dPA68BchyCY7
v9fGY+ImO6Jmx5u/SI3d
=+Nry
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to