Bug#435053: gcj-4.2: FTBFS on kfreebsd-amd64

Package: gcj-4.2 Version: 4.2.1-1 Severity: important Tags: patch gcj-4.2 fails to build on kfreebsd-amd64 at this architecture is still in java_no_archs. The patch below removes it, and it is the only thing need to get gcj working correctly on this architecture. diff -u gcj-4.2-4.2.1/debian/rul

[bts-link] source package gcc-snapshot

# # bts-link upstream status pull for source package gcc-snapshot # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #403596 # * http://gcc.gnu.org/PR29478 # * remote status changed: ASSIGNED -> NEW usertags 403596 - sta

gcc-4.2_4.2.1-1_m68k.changes ACCEPTED

Accepted: cpp-4.2_4.2.1-1_m68k.deb to pool/main/g/gcc-4.2/cpp-4.2_4.2.1-1_m68k.deb fixincludes_4.2.1-1_m68k.deb to pool/main/g/gcc-4.2/fixincludes_4.2.1-1_m68k.deb g++-4.2_4.2.1-1_m68k.deb to pool/main/g/gcc-4.2/g++-4.2_4.2.1-1_m68k.deb gcc-4.2-base_4.2.1-1_m68k.deb to pool/main/g/gcc-4.2/

Bug#407049: marked as done (gcc-3.4 / 64-bit libs in wrong location)

Your message dated Sat, 28 Jul 2007 22:17:10 + with message-id <[EMAIL PROTECTED]> and subject line Bug#407049: fixed in gcc-3.4 3.4.6ds1-6 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

Bug#420533: marked as done (utterly empty man page)

Your message dated Sat, 28 Jul 2007 22:17:10 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420533: fixed in gcc-3.4 3.4.6ds1-6 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

Processing of gcc-4.2_4.2.1-1_m68k.changes

gcc-4.2_4.2.1-1_m68k.changes uploaded successfully to localhost along with the files: gcc-4.2-base_4.2.1-1_m68k.deb libgcc2_4.2.1-1_m68k.deb libgomp1_4.2.1-1_m68k.deb cpp-4.2_4.2.1-1_m68k.deb protoize_4.2.1-1_m68k.deb fixincludes_4.2.1-1_m68k.deb libmudflap0-4.2-dev_4.2.1-1_m68k.deb

gcc-3.4_3.4.6ds1-6_multi.changes ACCEPTED

Accepted: cpp-3.4_3.4.6-6_i386.deb to pool/main/g/gcc-3.4/cpp-3.4_3.4.6-6_i386.deb cpp-3.4_3.4.6-6_powerpc.deb to pool/main/g/gcc-3.4/cpp-3.4_3.4.6-6_powerpc.deb g++-3.4_3.4.6-6_i386.deb to pool/main/g/gcc-3.4/g++-3.4_3.4.6-6_i386.deb g++-3.4_3.4.6-6_powerpc.deb to pool/main/g/gcc-3.4/g++-

Processing of gcc-3.4_3.4.6ds1-6_multi.changes

gcc-3.4_3.4.6ds1-6_multi.changes uploaded successfully to localhost along with the files: libstdc++6-dev_3.4.6-6_i386.deb gpc-2.1-3.4_3.4.6-6_powerpc.deb gcc-3.4-base_3.4.6-6_powerpc.deb gcc-3.4_3.4.6ds1-6.diff.gz cpp-3.4_3.4.6-6_i386.deb gcc-3.4_3.4.6-6_i386.deb gcc-3.4_3.4.6-6_power

Processed: merge gcc-3.4 report

Processing commands for [EMAIL PROTECTED]: > tag 379457 + wontfix Bug#379457: libg2c0-dev: Dangling symlink /usr/lib64/libg2c.so There were no tags set. Tags added: wontfix > severity 379457 minor Bug#379457: libg2c0-dev: Dangling symlink /usr/lib64/libg2c.so Severity set to `minor' from `normal'

Bug#434634: marked as done (gcc-4.2: [alpha] Regression in glibc testsuite)

Your message dated Sat, 28 Jul 2007 10:18:05 +0200 with message-id <[EMAIL PROTECTED]> and subject line gcc-4.2: [alpha] Regression in glibc testsuite 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