Bug#791044: geographiclib: library transition may be needed when GCC 5 is the default
On 03-08-15 14:40, Sebastiaan Couwenberg wrote: > On 19-07-15 20:40, Sebastiaan Couwenberg wrote: >> On 07/03/2015 03:10 PM, Matthias Klose wrote: >>> - 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. >> >> Just like pktools (#791240), geographic lib doesn't have any reverse >> dependencies. We'll only need to update the symbols on all architectures >> when the new libstdc++ is moved to unstable. > > It's currently not possible to build liblas due to uninstallable > dependencies, anything build depending on gdal will pull in libdap which > libstdc++ breaks. This is not the liblas bugreport, and fortunately geographiclib is not affects by uninstallable build dependencies, so I've uploaded geographiclib (1.43-3~exp1) to experimental with updates symbols for amd64 with GCC 5, I'll upload it to unstable after updating the symbols for the other architectures. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#791044: geographiclib: library transition may be needed when GCC 5 is the default
On 19-07-15 20:40, Sebastiaan Couwenberg wrote: > On 07/03/2015 03:10 PM, Matthias Klose wrote: >> - 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. > > Just like pktools (#791240), geographic lib doesn't have any reverse > dependencies. We'll only need to update the symbols on all architectures > when the new libstdc++ is moved to unstable. It's currently not possible to build liblas due to uninstallable dependencies, anything build depending on gdal will pull in libdap which libstdc++ breaks. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#791044: geographiclib: library transition may be needed when GCC 5 is the default
On 07/03/2015 03:10 PM, Matthias Klose wrote: > - 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. Just like pktools (#791240), geographic lib doesn't have any reverse dependencies. We'll only need to update the symbols on all architectures when the new libstdc++ is moved to unstable. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#791044: geographiclib: library transition may be needed when GCC 5 is the default
Package: src:geographiclib Version: 1.43-1 Severity: important Tags: sid stretch User: debian-...@lists.debian.org 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 cont...@bugs.debian.org: user release.debian@packages.debian.org usertag + transition block by 790756 reassign 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 ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
