Processed: fixed 667467 in 4.7.0-3

2012-04-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 667467 4.7.0-3 Bug #667467 [gcc-4.7-base] gcc-4.7-base: Uninstallable in M-A environment, due to different changelogs Bug #667645 [gcc-4.7-base] gcc-4.7-base: changelog.Debian.gz differs across architectures Marked as fixed in versions gcc

Processed: Re: Bug#667467: back in 4.7.0-5

2012-04-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 667467 Bug #667467 {Done: James McCoy } [gcc-4.7-base] gcc-4.7-base: Uninstallable in M-A environment, due to different changelogs Bug #667645 {Done: James McCoy } [gcc-4.7-base] gcc-4.7-base: changelog.Debian.gz differs across architectu

Bug#667467: back in 4.7.0-5

2012-04-29 Thread James McCoy
reopen 667467 found 667467 4.7.0-5 thanks On Sun, Apr 29, 2012 at 06:12:59PM -0500, Brian Paterni wrote: > bug may have come back to haunt us in 4.7.0-5?: Looks like it: $ zdiff -u gi386/usr/share/doc/gcc-4.7-base/changelog.Debian.gz gamd64/usr/share/doc/gcc-4.7-base/changelog.Debian.gz --- /de

Bug#667467: gcc-4.7-base: Uninstallable in M-A environment, due to different changelogs

2012-04-29 Thread Will Dyson
Broken again in 4.7.0-5 $ diff -u changelog.Debian.i386 changelog.Debian.amd64 --- changelog.Debian.i386 2012-04-29 19:12:54.012923225 -0400 +++ changelog.Debian.amd64 2012-04-29 19:11:17.000420781 -0400 @@ -13,7 +13,6 @@ [ Aurelien Jarno ] * Reenable parallel builds on GNU/kFreeB

Bug#667467: back in 4.7.0-5

2012-04-29 Thread Brian Paterni
bug may have come back to haunt us in 4.7.0-5?: Preparing to replace gcc-4.7-base:amd64 4.7.0-4 (using .../gcc-4.7-base_4.7.0-5_amd64.deb) ... De-configuring gcc-4.7-base:i386 ... Unpacking replacement gcc-4.7-base:amd64 ... Preparing to replace gcc-4.7-base:i386 4.7.0-4 (using .../gcc-4.7-base_

Results for 4.7.0 (Debian 4.7.0-5) testsuite on x86_64-pc-linux-gnu

2012-04-29 Thread Matthias Klose
LAST_UPDATED: Sat Apr 28 08:28:59 UTC 2012 (revision 186932) Target: x86_64-linux-gnu gcc version 4.7.0 (Debian 4.7.0-5) Native configuration is x86_64-pc-linux-gnu === g++ tests === Running target unix UNRESOLVED: attribute_plugin.c compilation, -I. -I/scratch/packages/gcc/4.

gcc-4.7_4.7.0-5_amd64.changes ACCEPTED into unstable

2012-04-29 Thread Debian FTP Masters
Accepted: cpp-4.7_4.7.0-5_amd64.deb to main/g/gcc-4.7/cpp-4.7_4.7.0-5_amd64.deb fixincludes_4.7.0-5_amd64.deb to main/g/gcc-4.7/fixincludes_4.7.0-5_amd64.deb g++-4.7-multilib_4.7.0-5_amd64.deb to main/g/gcc-4.7/g++-4.7-multilib_4.7.0-5_amd64.deb g++-4.7_4.7.0-5_amd64.deb to main/g/gcc-4.

Processing of gcc-4.7_4.7.0-5_amd64.changes

2012-04-29 Thread Debian FTP Masters
gcc-4.7_4.7.0-5_amd64.changes uploaded successfully to localhost along with the files: gcc-4.7_4.7.0-5.dsc gcc-4.7_4.7.0-5.diff.gz gcc-4.7-source_4.7.0-5_all.deb libstdc++6-4.7-doc_4.7.0-5_all.deb gcc-4.7-locales_4.7.0-5_all.deb gcc-4.7-base_4.7.0-5_amd64.deb libgcc1_4.7.0-5_amd64.deb

Bug#669858: marked as done (missing symbols in /lib64/libgcc_s.so.1)

2012-04-29 Thread Debian Bug Tracking System
Your message dated Sun, 29 Apr 2012 12:03:43 + with message-id and subject line Bug#669858: fixed in gcc-4.7 4.7.0-5 has caused the Debian Bug report #669858, regarding missing symbols in /lib64/libgcc_s.so.1 to be marked as done. This means that you claim that the problem has been dealt with

Bug#670821: gcc-4.6: build system treats systems that identify themselves as wheezy differently from systems that identify themselves as sid

2012-04-29 Thread peter green
Package: gcc-4.6 Version: 4.6.3-1 Severity: important Tags: patch While working on an unofficial "hardfloat for pi" port of debian I discovered that building the gcc-4.6 package in an environment that identifies itself (though lsb-release) as wheezy results in the build choosing different opti