We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable:
cpp-4.6 | 4.6.4-7 | amd64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x g++-4.6 | 4.6.4-7 | amd64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x g++-4.6-multilib | 4.6.4-7 | amd64, i386, kfreebsd-amd64, mips, mipsel, powerpc, s390x gcc-4.6 | 4.6.4-7 | source, amd64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x gcc-4.6-base | 4.6.4-7 | amd64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x gcc-4.6-locales | 4.6.4-7 | all gcc-4.6-multilib | 4.6.4-7 | amd64, i386, kfreebsd-amd64, mips, mipsel, powerpc, s390x gcc-4.6-plugin-dev | 4.6.4-7 | amd64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x gcc-4.6-source | 4.6.4-7 | all gfortran-4.6 | 4.6.4-7 | amd64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x gfortran-4.6-multilib | 4.6.4-7 | amd64, i386, kfreebsd-amd64, mips, mipsel, powerpc, s390x gobjc++-4.6 | 4.6.4-7 | amd64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x gobjc++-4.6-multilib | 4.6.4-7 | amd64, i386, kfreebsd-amd64, mips, mipsel, powerpc, s390x gobjc-4.6 | 4.6.4-7 | amd64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x gobjc-4.6-multilib | 4.6.4-7 | amd64, i386, kfreebsd-amd64, mips, mipsel, powerpc, s390x lib32objc3 | 4.6.4-7 | amd64, kfreebsd-amd64, s390x lib32objc3-dbg | 4.6.4-7 | amd64, kfreebsd-amd64, s390x lib32stdc++6-4.6-dbg | 4.6.4-7 | amd64, kfreebsd-amd64, s390x lib64objc3 | 4.6.4-7 | i386, mips, mipsel, powerpc lib64objc3-dbg | 4.6.4-7 | i386, mips, mipsel, powerpc lib64stdc++6-4.6-dbg | 4.6.4-7 | i386, mips, mipsel, powerpc libn32objc3 | 4.6.4-7 | mips, mipsel libn32objc3-dbg | 4.6.4-7 | mips, mipsel libn32stdc++6-4.6-dbg | 4.6.4-7 | mips, mipsel libobjc3 | 4.6.4-7 | amd64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x libobjc3-dbg | 4.6.4-7 | amd64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x libstdc++6-4.6-dbg | 4.6.4-7 | amd64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x libstdc++6-4.6-dev | 4.6.4-7 | amd64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x libstdc++6-4.6-doc | 4.6.4-7 | all libstdc++6-4.6-pic | 4.6.4-7 | amd64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x ------------------- Reason ------------------- RoQA; replaced by more recent GCC releases ---------------------------------------------- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 796...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/796274 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)