Your message dated Tue, 04 Aug 2015 10:00:41 +0000
with message-id <[email protected]>
and subject line Bug#791309: fixed in vpb-driver 4.2.59-1
has caused the Debian Bug report #791309,
regarding vpb-driver: 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.)


-- 
791309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791309
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:vpb-driver
Version: 4.2.58-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: vpb-driver
Source-Version: 4.2.59-1

We believe that the bug you reported is fixed in the latest version of
vpb-driver, 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.
Ron Lee <[email protected]> (supplier of updated vpb-driver 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: SHA1

Format: 1.8
Date: Tue, 04 Aug 2015 04:19:27 +0930
Source: vpb-driver
Binary: vpb-driver-source vpb-utils libvpb1 libvpb-dev libvpb-doc libvpb-dbg
Architecture: source amd64 all
Version: 4.2.59-1
Distribution: unstable
Urgency: medium
Maintainer: Ron Lee <[email protected]>
Changed-By: Ron Lee <[email protected]>
Description:
 libvpb-dbg - debugging symbols for libvpb and vpb-utils
 libvpb-dev - Voicetronix telephony hardware userspace library development file
 libvpb-doc - Voicetronix telephony interface library documentation
 libvpb1    - Voicetronix telephony hardware userspace interface library
 vpb-driver-source - Voicetronix telephony hardware driver source
 vpb-utils  - Voicetronix telephony hardware userspace tools
Closes: 791309
Changes:
 vpb-driver (4.2.59-1) unstable; urgency=medium
 .
   * Updates for gcc-5.  Closes: #791309
   * It makes some changes to libstdc++ which break ABI for us in a few places,
     mostly in symbols using std::basic_string or std::list, so we're going to
     bump the SONAME for this release, even though there is no incompatible
     change to the libvpb source itself.  In theory we could just rename the
     library package - but that would still leave people with out of distro
     applications screwed if they upgrade to the new package without rebuilding
     their own applications.  This way they'll at least fail loudly and early.
Checksums-Sha1:
 369810db4903bd6266fffeccaac4c6bd20d55581 2010 vpb-driver_4.2.59-1.dsc
 2e7a57d0f1bbbc41e2b6a7f94bd6bc60d6a36b68 686725 vpb-driver_4.2.59.orig.tar.gz
 c1603ca8ba4ab48a02a33edc7bb533ebb74672f1 16579 vpb-driver_4.2.59-1.diff.gz
 e1257c8776189ed3ccd70901198c3b599989df8c 854224 libvpb-dbg_4.2.59-1_amd64.deb
 8ecde308ac13799ed23d10268137d7fa5d5e1893 186776 libvpb-dev_4.2.59-1_amd64.deb
 515f9701c8a5a5a5f5850c1d5a90ed54732dc05a 5099628 libvpb-doc_4.2.59-1_all.deb
 a5014ed1bfc2ca84915c8821b223f59db66d75e9 155124 libvpb1_4.2.59-1_amd64.deb
 3dc8c30080754f3089a1ba7b729e9a1b925c8dc5 84148 
vpb-driver-source_4.2.59-1_all.deb
 d60975dad2cf4d8fe5fbd92a5381314d2f98951b 52302 vpb-utils_4.2.59-1_amd64.deb
Checksums-Sha256:
 a86d277732e14c04aac5084a2d5367d59f7c98aa19ca951a319b352bbe8b7f46 2010 
vpb-driver_4.2.59-1.dsc
 2aa9dd6fb7a195ba889eb19c1cfa90eb93fd32678e7dac68d779331e97670fe7 686725 
vpb-driver_4.2.59.orig.tar.gz
 fa8401fe75751db378ae6435289523c3be4116022c4445940fc7df581cfd92d3 16579 
vpb-driver_4.2.59-1.diff.gz
 ef4da4953e240137db107406bd977ced34539a179302f90b33d4fcf232969612 854224 
libvpb-dbg_4.2.59-1_amd64.deb
 a784cb6b7b5c8d828beb4cf947401f3426587721f337c70d65f15b1a3a09885f 186776 
libvpb-dev_4.2.59-1_amd64.deb
 67056f9b9711305c1e67bb50f118dbc06017e6bc8a318b9579e5e913b0ba0da0 5099628 
libvpb-doc_4.2.59-1_all.deb
 9ac46b65775dc1364089acfceebd42e12385c1719a68f9c6099780da89ac1892 155124 
libvpb1_4.2.59-1_amd64.deb
 ffb3e7db84916fc6bb6806074a15ff473a90cfa2a2fdc9493396821d0bd0863b 84148 
vpb-driver-source_4.2.59-1_all.deb
 0b167b2f9d68bb5d7822cf5dd89f30997e34c72f39371aca23da3170e268acad 52302 
vpb-utils_4.2.59-1_amd64.deb
Files:
 3d4560c14c7183b831f101fa3e806577 2010 comm optional vpb-driver_4.2.59-1.dsc
 8064329e4a56a93b21c88a7ca0de2668 686725 comm optional 
vpb-driver_4.2.59.orig.tar.gz
 15c9a4a0b37773b32f9af46130ec1daa 16579 comm optional 
vpb-driver_4.2.59-1.diff.gz
 cfa97a433b8fad1911ce08f5d00632ea 854224 debug extra 
libvpb-dbg_4.2.59-1_amd64.deb
 81a9a634250680e3238f0c8a1e1cc65e 186776 libdevel optional 
libvpb-dev_4.2.59-1_amd64.deb
 a6e868af64d0aa9a8638bc51716af402 5099628 doc optional 
libvpb-doc_4.2.59-1_all.deb
 137cc32aff8053e3b2fd09132ede2d84 155124 libs optional 
libvpb1_4.2.59-1_amd64.deb
 2daab680ff56069186f43880ed74c21b 84148 kernel optional 
vpb-driver-source_4.2.59-1_all.deb
 0818d6c6183df196cbf01a66bbaab02f 52302 comm optional 
vpb-utils_4.2.59-1_amd64.deb

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

iQIcBAEBAgAGBQJVv8b0AAoJECSWn9pgwHEsn9IQAKI5AoSHtJdzky7avQ0PxMp/
UFIx93h6mc9mmckEpUrx5bEN69tiY3+NFRfFJ5GrDtRNC6EzorKDDM7He40c1wa9
21epGqieLNHDZnfrR5ONjXDuBWZekOwulDLrBx9mHHzL+22fKT1dN8BWwB54agy+
9Gjxfi/L7lrtwQhvO8n9TjTH6xu5U5rTDydJiUUwQH/L6ueM+9+yUhoZyHCkMTkT
OxChVEohWW7LipPo8wh7j+6WW09ZinaiZEWL26Q1pIvebexk8YPrfOXkqc+z+AB6
TtJp+L2riAegU2CMgJ2yXNA5No0liCBF3oJfcDJrS5qAtCTFBHUQqbFprDfOrI/1
u8eSuQDIxWs1SW3IITfWHfKBBaYNJQU+/p4f0uYVI4q0h3Cr6VYrgGLrYbXGKnsk
bEmLFqVinkj+f248JotS1qctvdkWqootv1MluImLvmAdXk7nisdi8FVuh4QwaS9r
yjOEBow0kAIlasPVCIQBlBE6PEPi0hYSj9mSPyFQmEfgJRuXgnLD/gPlKUNcVw6h
43EdWWdt6PsAQTHOs2z2BlvTKTO99XnQGmXt0BVjh4kgaydEwLj6tAvSgk7wfsGg
4eHuWh66KZ8uJA8e9MWY3rPIEjlUiPKf4S5harwGvrHc/41T/gQhaZ8Se4eLLc1z
qDUiwOYO+fZp4ekBhYJM
=Ndkf
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to