Follow-up transitions for the libstdc++6 ABI changes
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Finally sid deserves its name again. GCC 5 is now the default in unstable and
packages for the follow-up transitions are (and can be) uploaded to unstable.
What you should *not* do:
- upload a library package with an open transition issue [1]
without renaming the library package or bumping the soname,
just saying "Rebuild with GCC 5", and silently breaking the ABI.
- upload a package which builds a C++ library package, which
is built with anything else than g++-5.
- having a vacation and hoping the mess is cleaned up when
you come back.
What should be done:
- Fix the open transition issues, making sure that all other
transitions in the build dependencies are done, and tighten
the build dependencies to the version making the ABI change.
- The buildds for all release architectures have GCC 5 as the
default, some of the buildds for the ports are lagging. If
you want to add a b-d on g++, b-d on g++ (>= 4:5.2). This
could be removed again later.
- Adopt a follow-up library transition. The majority of the
of the library transition issues doesn't have any feedback
from the package maintainers. If something blocks you,
please care about these transitions. The release team lowered
the NMU threshold for these packages [2].
- Fix the other outstanding issues introduced by GCC 5 [3].
- If you do (mass) test rebuilds, and you see link failures,
please don't file bug reports for these packages (yet).
These are most likely caused by not yet transitioned build
dependencies. Please make sure that such a bug report [1]
exists or is already a dependency of #790756 [4]; and if not,
please file a new one, mentioning which package fails to build.
Currently gcc-5 is blocked in unstable (#794184). It is planned to close this
issue once many follow-up library transitions are started, and the follow-up
transitions are blocked on their own by unfulfillable dependencies.
Thanks for getting to the point where we could make GCC 5 the default, fixing
hundreds of issues, thanks to package maintainers fixing issues them self, to
David Suarez for test rebuilds, to our NMU machine gun Gregor Herrmann, to the
kind people of HP organized by Martin Michlmayer, and anybody else helping
with these fixes.
Matthias
[1]
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=libstdc%2B%2B-cxx11;users=debian-gcc@lists.debian.org
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg00000.html
[3]
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-gcc-5;users=debian-gcc@lists.debian.org
[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790756
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJVv0cZAAoJEL1+qmB3j6b1newP/1ArNTXKYuWUxK29AYz3Ll4K
qjgjK3dGZKYMk8eHCPjZxNANXa2F3uE0zDdmL2ib3A0/M1yp801L6mQIukZqgKpU
CnBL/RgL8p9Ze+CGpw1MijaAAxqBTUm2Zt9348/QtLzE90ofDZXEIEqH45UJ7JyQ
+x/lcJjPEFTsL+9y7A19IMLDmKzRUht1YEqL9tK8jSRkWtO/HiI5DAmss7PPxLP4
UWG01YE9VNKLaD7/J/a4g24o/3e7SvLHNa5vGv2/mRKeHgDeXUCHWSyqcD/r+t86
rDqpC4rVtj+t7nhLCsJTc/j01pRgpIFv79Pqdv5qaNwtsPhJkG+BQIhPAM8JXhBw
zRBvbBOzYJR3yX92fD2eA9mOlBH40n07HgXj1Jlb7Tpt4T/gsdzHz4+TSJu9ivQs
QWKqNj4oito8dqU/MKIKPcUsVSUWduETVimhej7sE0vNNnIrxNMevRHlBP2/de/7
BTQuOdChGIaNlYWD+6R6qTLdeCj1CUT6a/EOAqwo+jXAWOh+0VtQJSUC+ugDhFwW
a+khOXyKDaNFKcA2ezvzXSsQmgRwBqEd43L/Wza4ln458YZebSlGXQnfZ0L3bp60
fhFTojijLKJAJRLViEkULiUuNABMMLB6KN9ta2yuYz/XBu9+ZPY8HEw/U2aVAts3
kOvO6iNwx1F+Xvdf7eCc
=sTds
-----END PGP SIGNATURE-----
Reply to: