Your message dated Fri, 15 Jan 2016 10:00:47 +0000
with message-id <[email protected]>
and subject line Bug#791219: fixed in ns3 3.22+dfsg-2
has caused the Debian Bug report #791219,
regarding ns3: 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.)
--
791219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791219
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:ns3
Version: 3.22+dfsg-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: ns3
Source-Version: 3.22+dfsg-2
We believe that the bug you reported is fixed in the latest version of
ns3, 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.
Martin Quinson <[email protected]> (supplier of updated ns3 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: Thu, 07 Jan 2016 23:00:44 +0100
Source: ns3
Binary: ns3 ns3-doc libns3-3v5 libns3-dev python-ns3
Architecture: source amd64 all
Version: 3.22+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Network Simulators Team
<[email protected]>
Changed-By: Martin Quinson <[email protected]>
Description:
libns3-3v5 - shared libraries of ns-3
libns3-dev - Static and header files of ns-3
ns3 - discrete-event network simulator for Internet systems
ns3-doc - documentation for ns3
python-ns3 - Python binding of ns3
Closes: 715096 788478 791219 807219
Changes:
ns3 (3.22+dfsg-2) unstable; urgency=medium
.
* Add myself to the uploaders.
* Update build dependencies for GSL 2.x (Closes: #807219)
Thanks to Bas Couwenberg for the patch.
* Update the watch file from the sepwatch project.
* Make the build reproducible by faking the doc generation date
(Closes: #788478) Thanks to Juan Picca for the patch.
* Transition the library package for GCC5 (Closes: #791219)
* Don't build manually the dbg packages. It's automatic nowadays
* Have libns3-dev depend on libns3-3v5 as it should (Closes: #715096)
Checksums-Sha1:
da0fbbcd17f96ed74ee8b1089a849e32a068529b 2593 ns3_3.22+dfsg-2.dsc
3b90f60e53320ef5477b7ae2383317756f3c3241 238868 ns3_3.22+dfsg-2.debian.tar.xz
72fcff224391be0099fda1763df572fde0c65d5b 84911968
libns3-3v5-dbgsym_3.22+dfsg-2_amd64.deb
2414d595624b36e09d701c7d9f1cbe4d41d90179 7822666
libns3-3v5_3.22+dfsg-2_amd64.deb
eaa28344341a53511f7f32f4893f63fedcf55d97 6564546
libns3-dev_3.22+dfsg-2_amd64.deb
684b6dd986fd53d8e807a8ee8e5798f7190eeda4 571284
ns3-dbgsym_3.22+dfsg-2_amd64.deb
fcc8b3071bbb4048258996c3bc1f6b8f7c937a87 7880320 ns3-doc_3.22+dfsg-2_all.deb
1591cc1a9d707ccafb54a40eb6bf4e5a7d7ad151 149248 ns3_3.22+dfsg-2_amd64.deb
2ac320e27c5c772688e02d854ec97251a748c499 25459460
python-ns3-dbgsym_3.22+dfsg-2_amd64.deb
8693752ce9f96c073b9368be1c0f0f569ea66713 2970602
python-ns3_3.22+dfsg-2_amd64.deb
Checksums-Sha256:
d453cc89c9e224d4b75e6baa2deddb886313d9d3d0badb7660a12bb87e16fb89 2593
ns3_3.22+dfsg-2.dsc
82c6054c32e993b43bd738c61972785d9e44912515e559a09c19bee495f813b8 238868
ns3_3.22+dfsg-2.debian.tar.xz
317aa9343e2300c14fb4ddc576efbccb2e1b6b936ff76c98880b5510a5095313 84911968
libns3-3v5-dbgsym_3.22+dfsg-2_amd64.deb
c72cce1c62ebfdad386bc8f1596d7f028960a3ff609c07221fdb0732bafb0918 7822666
libns3-3v5_3.22+dfsg-2_amd64.deb
eb61508b97c7fd6aac2710550824c7ff1250c3029c3e46483bcaebcde1986200 6564546
libns3-dev_3.22+dfsg-2_amd64.deb
7cb36a1eb6d698f1a6cf37145e403586bb541e991a521fa94365b2a3f8837dc2 571284
ns3-dbgsym_3.22+dfsg-2_amd64.deb
2133e81bfdd70f30e4d9fc9d49b2c81eeaf3ac7f342a93de544a35bd65d445c0 7880320
ns3-doc_3.22+dfsg-2_all.deb
e961a9fb3503b68a7d4b8d026e4997c00a5b9dd2565b26f98b6a0e7f5bd1db44 149248
ns3_3.22+dfsg-2_amd64.deb
7f12f54d3f7d9909dffa0f89bf0d5e09fdefc79e25ed154ae9fce235998ebd92 25459460
python-ns3-dbgsym_3.22+dfsg-2_amd64.deb
1786bccbcbdb7d6c4a406b81b76c7563e1ee0a7ff9095e6d3a4ec349a4d052ac 2970602
python-ns3_3.22+dfsg-2_amd64.deb
Files:
412f8fda8a951b90545a51dcc64c01e9 2593 net optional ns3_3.22+dfsg-2.dsc
4f3ab480d75ed91597f26a9f5de4c1e5 238868 net optional
ns3_3.22+dfsg-2.debian.tar.xz
d1bad655734f6e40e31b367e90512348 84911968 debug extra
libns3-3v5-dbgsym_3.22+dfsg-2_amd64.deb
7faeffb52c39ade92af4b4847b1e6b4b 7822666 net optional
libns3-3v5_3.22+dfsg-2_amd64.deb
d595ee4ad333d78c13c42ec0f955727b 6564546 libdevel optional
libns3-dev_3.22+dfsg-2_amd64.deb
02c785b61ecdd700a52ad0938b5b12a2 571284 debug extra
ns3-dbgsym_3.22+dfsg-2_amd64.deb
39e821cb34d938744e28e1b51d17faf8 7880320 doc optional
ns3-doc_3.22+dfsg-2_all.deb
6267b5ca9a861e58b0fb95891db20ab9 149248 net optional ns3_3.22+dfsg-2_amd64.deb
43282f5407f0bf1ff7384be4a1f03c66 25459460 debug extra
python-ns3-dbgsym_3.22+dfsg-2_amd64.deb
c8a417cfe1dec2d2e2226eef911ea627 2970602 python optional
python-ns3_3.22+dfsg-2_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJWmBuRAAoJEJi9lyRPc76n7SYP/0VzPSF1B08beLbsgsBm5jc8
CqQgYOA+aNB6fVZdpzQfG1YRO1eaeTdWek7t7QFO/tW0rp660u7+fRJc6mdywJd3
/Wra8Uv4OXc21vQ9zvbju12r19ZfjMAQD/mcYOSDdcDTDfr25J4+W1Pw/3iKDaBJ
Azf7F2xwQDL8s+2ivLwgFKbyKRn5axCezIwZL6ZysTdjx74GQ9UTrPgUsCwHv+vb
9N2dDDoF4tns1D76aWJgt8KhBa1Sd9XfxaiI7LnhYlh8teTRwxrHDLTdMILsPGXb
ty65ztl8kNLUMdJKeqZ7N0iIoeusUSRq6LjB/Hf4Ha2AHu4sa6XGSCZEY6LxIvN1
3VkbIKjrBwVj4qoBlJOw99h8cLvqGiqLdi7+hflHLbeZp3PE8XAv7uoN9FR4BBCg
+zCJlwWoclJOimVGb6A2wF+KGUx0FA2arYa0ObYrQb6rVa5xchqtW6HzU9rCNMMm
jh0jOigeTlN/Jp3RopJgpHj4RaqPyy69umDKG9GgtMAXwGaWzSxCn5LwN9+7LhZt
qUjPh1tXrJItTMOzfGLXks1RE8X+cZBw5mv4o68qf2dVoroqZsEc+vcKJagw7Gl/
8G8XQsmOgBTqRbh2aHNKGrcMM5UIig/ALteiOa/6yzXl9VlVBu9+QqViX2RErszS
Cne6k81zI1dR88IdbVEQ
=GNNn
-----END PGP SIGNATURE-----
--- End Message ---
