Bug#629868: When it changed

This isn't definitive, but a 10 minute binary search of snapshot.debian.org lead me to the point where the size took a dive. If snapshot.debian.org has an ftp interface this would have taken less time. http://snapshot.debian.org/archive/debian/20100501T040743Z/pool/main/g/gcc-4.5/ - libstdc++6

Bug#602785: closed by Debian FTP Masters (Bug#675431: Removed package(s) from unstable)

reopen 602875 reassign 602875 gcc-4.7 kthxbye On Sat, Aug 25, 2012 at 12:03:18PM +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the gcc-4.5 package: > > #602785: gcc-4.5: should optimize bitwise operations > > It h

Processed: Re: Bug#602785 closed by Debian FTP Masters (Bug#675431: Removed package(s) from unstable)

Processing commands for cont...@bugs.debian.org: > reopen 602875 Bug #602875 [epiphany-browser] epiphany-browser: passwords lost after upgrade from lenny to squeeze Bug 602875 is not marked as done; doing nothing. > reassign 602875 gcc-4.7 Bug #602875 [epiphany-browser] epiphany-browser: password

Processed: Retitle

Processing commands for cont...@bugs.debian.org: > retitle 630892 Please remove the dependency on g++-X from the libstdc++ Bug #630892 {Done: Debian FTP Masters } [libstdc++6-4.7-dev] libstdc++6-4.7-dev: Changed Bug title to 'Please remove the dependency on g++-X f

Processed (with 1 errors): Retitle

Processing commands for cont...@bugs.debian.org: > retitle 630892 libstdc++6-4.7-dev: Bug #630892 {Done: Debian FTP Masters } [libstdc++6-4.7-dev] libstdc++6-4.5-dev: Please remove the dependency on g++-4.5 Changed Bug title to ' libs

Processed: reassign

Processing commands for cont...@bugs.debian.org: > reassign 630892 libstdc++6-4.7-dev Bug #630892 {Done: Debian FTP Masters } [libstdc++6-4.5-dev] libstdc++6-4.5-dev: Please remove the dependency on g++-4.5 Bug reassigned from package 'libstdc++6-4.5-dev' to 'libstdc++6-4.7-dev'. No longer marked

Bug#675431: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: cpp-4.5 |4.5.4-1 | amd64, armel, armhf, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc g++-4.5 |4.5.4-1 | amd64, armel, armhf

Bug#681762: marked as done (gcc-4.5 FTBFS on alpha: Failed link; work around is to link with --no-relax)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #681762, regarding gcc-4.5 FTBFS on alpha: Failed link; work around is to link with --no-relax to be marked as done. This means that

Bug#659001: marked as done (libstdc++6-4.5-dbg: python file in /usr/lib/x86_64-linux-gnu triggers ldconfig warnings)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #659001, regarding libstdc++6-4.5-dbg: python file in /usr/lib/x86_64-linux-gnu triggers ldconfig warnings to be marked as done. This

Bug#629868: marked as done (libstdc++.tag not installed by libstdc++6-4.5-doc)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #629868, regarding libstdc++.tag not installed by libstdc++6-4.5-doc to be marked as done. This means that you claim that the problem h

Bug#626240: marked as done (gcc-4.5: Spurious array bounds warning)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #626240, regarding gcc-4.5: Spurious array bounds warning to be marked as done. This means that you claim that the problem has been dea

Bug#630892: marked as done (libstdc++6-4.5-dev: Please remove the dependency on g++-4.5)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #630892, regarding libstdc++6-4.5-dev: Please remove the dependency on g++-4.5 to be marked as done. This means that you claim that the

Bug#624354: marked as done (./xpcshell: error while loading shared libraries: ./libxul.so: R_PPC_REL24 relocation at 0x0f9f0148 for symbol `_restgpr_29_x' out of range)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #624354, regarding ./xpcshell: error while loading shared libraries: ./libxul.so: R_PPC_REL24 relocation at 0x0f9f0148 for symbol `_res

Bug#621420: marked as done (Misbuilds busybox on ARM)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #621420, regarding Misbuilds busybox on ARM to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#618386: marked as done (gcc-4.5: fails to vectorize trivial loop with aligned operands)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #618386, regarding gcc-4.5: fails to vectorize trivial loop with aligned operands to be marked as done. This means that you claim that

Bug#619130: marked as done (ERROR: compile in g++-4.5)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #619130, regarding ERROR: compile in g++-4.5 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#617968: marked as done (libstdc++6-4.5-dev: Apps that include FTBFS)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #617968, regarding libstdc++6-4.5-dev: Apps that include FTBFS to be marked as done. This means that you claim that the problem has be

Bug#597090: marked as done (libstdc++6-4.5-dev: several STL classes implicitly add to the exception specification of containing classes' destructors)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #597090, regarding libstdc++6-4.5-dev: several STL classes implicitly add to the exception specification of containing classes' destruc

Bug#602785: marked as done (gcc-4.5: should optimize bitwise operations)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #602785, regarding gcc-4.5: should optimize bitwise operations to be marked as done. This means that you claim that the problem has bee

Bug#611911: marked as done (/lib64/libpthread.so.0: could not read symbols: Invalid operation)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #611911, regarding /lib64/libpthread.so.0: could not read symbols: Invalid operation to be marked as done. This means that you claim th

Bug#594062: marked as done (gcc-4.5: -flto and #pragma GCC optimize are incompatible)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #594062, regarding gcc-4.5: -flto and #pragma GCC optimize are incompatible to be marked as done. This means that you claim that the pr

Bug#575997: marked as done (libstdc++6-4.5-dev: c++config.h doesn't seem to match reality)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #575997, regarding libstdc++6-4.5-dev: c++config.h doesn't seem to match reality to be marked as done. This means that you claim that t

Bug#564984: marked as done (warning if DBL_MIN is used in conjunction with -Wold-style-cast)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #564984, regarding warning if DBL_MIN is used in conjunction with -Wold-style-cast to be marked as done. This means that you claim that

Bug#566064: marked as done (gcc-4.5: regression - constant storage size not detected properly)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #566064, regarding gcc-4.5: regression - constant storage size not detected properly to be marked as done. This means that you claim th

Bug#498934: marked as done (priority required still necessary?)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #498934, regarding priority required still necessary? to be marked as done. This means that you claim that the problem has been dealt w

Bug#562882: marked as done (please add gengtype)

Your message dated Sat, 25 Aug 2012 12:01:11 + with message-id and subject line Bug#675431: Removed package(s) from unstable has caused the Debian Bug report #562882, regarding please add gengtype to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: Fails to build bsnes in wheezy

Processing control commands: > fixed -1 4.7.1-6 Bug #685845 [g++-4.7] Fails to build bsnes in wheezy Marked as fixed in versions gcc-4.7/4.7.1-6. > block 684840 by -1 Bug #684840 [src:bsnes] bsnes: FTBFS: sort.hpp:73: multiple definition of `void nall::sort(nall::string*, unsigned int)::{lambda(n

Bug#685845: Fails to build bsnes in wheezy

Package: g++-4.7 Version: 4.7.1-2 Severity: important Control: fixed -1 4.7.1-6 Control: block 684840 by -1 Hi, I think that bsnes 0.088-3 FTBFS in Wheezy (#684840), because of a bug in gcc. Linking fails with an error message I can't make sense of: > obj/ui-config.o: In function `void nall::sor