Results for 3.4.2 (Debian 3.4.2-3) testsuite on powerpc-linux

2004-10-18 Thread Matthias Klose
LAST_UPDATED: Obtained from CVS: -rgcc_3_4_2_release Native configuration is powerpc-linux (voltaire) === gpc tests === Running target any === gpc Summary === # of tests3953 # of expected passes 3948 # of unsupported tests5 /build/buil

Results for 3.4.2 (Debian 3.4.2-3) testsuite on ia64-linux

2004-10-18 Thread Matthias Klose
LAST_UPDATED: Obtained from CVS: -rgcc_3_4_2_release Native configuration is ia64-linux (caballero) === gpc tests === Running target any FAIL: fjf512.pas FAIL: fjf762a.pas FAIL: math.pas === gpc Summary === # of tests3953 # of expected passes

Bug#277115: marked as done (gcc-3.5: FTBFS on Sarge i386)

2004-10-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 Oct 2004 23:13:19 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#277115: gcc-3.5: FTBFS on Sarge i386 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

Bug#277128: required depends on optional

2004-10-18 Thread Matthias Klose
reassign 277128 ftp.debian.org retitle 277128 lib64gcc1 priority thanks yes, the override file needs modification. Marcel Sebek writes: > Package: lib64gcc1 > Severity: normal > > > Package lib64gcc1 is priority required but depends on amd64-libs, > which is priority optional. That violates Deb

Processed: Re: Bug#277128: required depends on optional

2004-10-18 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reassign 277128 ftp.debian.org Bug#277128: required depends on optional Bug reassigned from package `lib64gcc1' to `ftp.debian.org'. > retitle 277128 lib64gcc1 priority Bug#277128: required depends on optional Changed Bug title. > thanks Stopping proc

Bug#277129: marked as done (gcc-3.3 1:3.3.4-13 FTBFS due to missing build-dep on realpath)

2004-10-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 Oct 2004 22:54:42 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#277129: gcc-3.3 1:3.3.4-13 FTBFS due to missing build-dep on realpath has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with

Bug#277128: required depends on optional

2004-10-18 Thread Marcel Sebek
Package: lib64gcc1 Severity: normal Package lib64gcc1 is priority required but depends on amd64-libs, which is priority optional. That violates Debian Policy. --- cut --- 2.5. Priorities --- . . . Packages must not depend on packages with lower priority values (excludi

Bug#277129: gcc-3.3 1:3.3.4-13 FTBFS due to missing build-dep on realpath

2004-10-18 Thread Len Sorensen
Package: gcc-3.3 Version: 1:3.3.4-13 Severity: serious Justification: no longer builds from source I was trying to build a gcc-3.3.4 cross compiler for arm, but my build failed with a missing 'realpath' command, which seems to be provided by the package 'realpath'. Should gcc-3.3 source build-dep

Bug#277115: gcc-3.5: FTBFS on Sarge i386

2004-10-18 Thread Faheem Mitha
Package: gcc-3.5 Version: 3.5-0pre1 Severity: serious Tags: experimental Justification: Policy 4.2 I tried compiling gcc-3.5 on my system, with the usual apt-get build-dep ... and debuild binary. It crashed towards the end with the following error. This should be easy to reproduce. As you can

Bug#179018: marked as done (gcc-3.2: [m68k] segfaults when building xemacs21)

2004-10-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 Oct 2004 07:59:22 +0200 with message-id <[EMAIL PROTECTED]> and subject line xemacs21 is current on m68k has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your respon

Bug#176629: marked as done (gij-3.2: package incorrctly provides java1-runtime )

2004-10-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 Oct 2004 07:56:46 +0200 with message-id <[EMAIL PROTECTED]> and subject line gij-3.x: package incorrctly provides java1-runtime has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the cas