severity 335638 minor thanks On Tue, Oct 25, 2005 at 01:26:04AM -0400, Nathanael Nerode wrote: > So blackbook needs to deal with the C++ ABI transition. > Details of the transition are at: > http://lists.debian.org/debian-devel-announce/2005/07/msg00001.html
This is not an RC bug in the blackbook package. Bugs for the C++ ABI transition are RC if: - the package builds a library exporting a C++ interface, and rebuilding results in ABI breakage - the package fails to build with g++-4.0 - the package depends on a library other than libstdc++, and therefore must be rebuilt or removed from testing in order to let the transition move forward for other packages. blackbook is a standalone application with a dependency on libstdc++ only. > However, according to http://blackbook.sourceforge.net/ , > "Blackbook is no longer developed or maintained. The coding style is not > compatible with the newer GCCs and the author is not willing to fix it." > Accordingly, it may fail to compile with g++-3.4 or g++-4.0. In this > case you have several options: > -- Fix it yourself, effectively becoming upstream > -- Build-Depend on g++-3.3 and carefully change all the Makefiles to > make sure it uses it *If* the package fails to build with the default compiler, then this bug is RC; but that seems unlikely, given that people have been running full-archive rebuild tests on a regular basis and this bug has not yet been reported. Oh, and build-depending on g++-3.3 is not likely to be an option for etch; the last package using it, openoffice, has just switched to g++-4.0, and the gcc maintainer intends to drop it in the next gcc-3.3 upload. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
