Your message dated Thu, 20 Aug 2015 16:01:07 +0000
with message-id <[email protected]>
and subject line Bug#791316: fixed in yaml-cpp0.3 0.3.0-1.2
has caused the Debian Bug report #791316,
regarding yaml-cpp0.3: 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.)


-- 
791316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791316
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:yaml-cpp0.3
Version: 0.3.0-1.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: yaml-cpp0.3
Source-Version: 0.3.0-1.2

We believe that the bug you reported is fixed in the latest version of
yaml-cpp0.3, 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.
Julien Cristau <[email protected]> (supplier of updated yaml-cpp0.3 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: Sun, 16 Aug 2015 17:56:56 +0200
Source: yaml-cpp0.3
Binary: libyaml-cpp0.3v5 libyaml-cpp0.3-dev
Architecture: source amd64
Version: 0.3.0-1.2
Distribution: unstable
Urgency: medium
Maintainer: Lifeng Sun <[email protected]>
Changed-By: Julien Cristau <[email protected]>
Description:
 libyaml-cpp0.3-dev - YAML parser and emitter for C++ - development files (0.3 
series)
 libyaml-cpp0.3v5 - YAML parser and emitter for C++ (0.3 series)
Closes: 791316
Changes:
 yaml-cpp0.3 (0.3.0-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rename library packages for g++5 ABI transition (closes: 791316).
Checksums-Sha1:
 16f6a4cadc57180fb2fc05e856bef88cec3dea5b 1861 yaml-cpp0.3_0.3.0-1.2.dsc
 36d2af3e55509161b4b9535171a1e82e210e5cbc 2824 
yaml-cpp0.3_0.3.0-1.2.debian.tar.xz
 b0c58ad19aa4f301d69529bf4b3d9473ece058ab 176538 
libyaml-cpp0.3-dev_0.3.0-1.2_amd64.deb
 7ad72af00678417f7a0612e7bd66599dc6669307 145158 
libyaml-cpp0.3v5_0.3.0-1.2_amd64.deb
Checksums-Sha256:
 e05c88cc018eb1479c6e176d5bf27bc3d9ab43001b03df2c0a2668c166f5aa4d 1861 
yaml-cpp0.3_0.3.0-1.2.dsc
 6233e12153e3843ade7bbf1993645e23e953c779fce91a784df03635f0e7846d 2824 
yaml-cpp0.3_0.3.0-1.2.debian.tar.xz
 d678659d63f7cd47842c5cc2d24c5f3e566c5009cb47aa598cfd2c19a8ef1de7 176538 
libyaml-cpp0.3-dev_0.3.0-1.2_amd64.deb
 a4a431ef61456cdb186b5fe7bee002a1e262bf8ba338636d5b8785766ebf0266 145158 
libyaml-cpp0.3v5_0.3.0-1.2_amd64.deb
Files:
 f36077d654d709872ac75732c9a60c61 1861 devel optional yaml-cpp0.3_0.3.0-1.2.dsc
 e9845c417c76d4599aad5b5a0c22494d 2824 devel optional 
yaml-cpp0.3_0.3.0-1.2.debian.tar.xz
 7c70dd1774056dbd07d51e92be00b982 176538 libdevel optional 
libyaml-cpp0.3-dev_0.3.0-1.2_amd64.deb
 d0f4392c4b9a46e0542856bfb1fe28fa 145158 libs optional 
libyaml-cpp0.3v5_0.3.0-1.2_amd64.deb

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

iQIcBAEBCAAGBQJV0jBcAAoJEDEBgAUJBeQM5+sQAMUr95Ci+/bMblyugTivbKPC
444SFA6WdG1B56km6Ynyi/+LAacPg4LWx3SFsG6oTFB9HT29mFe4OE1QVDgBeZva
rKwKEoNJuwItaOn9DodGjxk/mcL/e81Ty1gQbKQXq+8GcAk7pqmuiOR8IXWNVsjb
4+kBbQ+boQOBfbxDY+TqA5MxBAgtbAZyrsDX/B5zYIEQSNWh2fjlWAAkeB+ThRVa
3rxVOVCYT9zUnal8xxymu/wJ4oO+KK00X5tLT6B+xKX6Ig0rs8GeBdHB2Cv4bIJS
c77xuhSuNJXFIinNUxiR9B55ygYHa8ELgH34X0pDniOfWr0gOQM9j/XgkwvuZMSq
4O4Zqa3zSWdgRBzYDyfI1gTO0UxBDaERTLKQfKhD558JDIiATU57+CxGXYdaH4ig
v/uxOa2HYuQmfmUmV7rhg4LtgGKS/JnmHlHkyVahNYRq7Kj/Jj89Pl0GffBcyN5D
MZ7wyaWeo97530BhN9G6b5iXbZ7L38RUvUmhnggRuT7QMv2ozECaRq489TpC6iqn
nHdOoHmiw3OUKb44qVKxZpmuxMDakdyRefWEr+d3toDpd3TSdvjpS7UD9CiUppeM
zI+xDFav5yEZPUI747TOk5je/HmZbuIiSNauxkV/zDMBOhKVT7heVlhkdysFYhGh
yMFDf3ccVtyyUb8WFpxs
=fZ+W
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to