Your message dated Sat, 25 Oct 2008 02:48:47 +0200 with message-id <[EMAIL PROTECTED]> and subject line closing bugs for gcc-3.4, which won't be fixed has caused the Debian Bug report #420533, regarding utterly empty man page 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 responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 420533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=420533 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems
--- Begin Message ---Package: gcc-3.4 Version: 3.4.6-5 Severity: normal [EMAIL PROTECTED]:~>man gcc-3.4|cat GCC(1) GNU GCC(1) gcc-3.4.6 2007-01-01 GCC(1) I think this should be removed. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.20-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gcc-3.4 depends on: ii binutils 2.17-3 The GNU assembler, linker and bina ii cpp-3.4 3.4.6-5 The GNU C preprocessor ii gcc-3.4-base 3.4.6-5 The GNU Compiler Collection (base ii libc6 2.5-2 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-21 GCC support library Versions of packages gcc-3.4 recommends: ii libc6-dev 2.5-2 GNU C Library: Development Librari -- no debconf information -- see shy josignature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---tag 471831 + wontfix tag 441104 + wontfix tag 452115 + wontfix tag 299188 + wontfix tag 420533 + wontfix tag 437537 + wontfix tag 378107 + wontfix tag 425053 + wontfix tag 323285 + wontfix tag 399100 + wontfix thanks closing bugs for gcc-3.4, which won't be fixed. either the binary package is not built anymore in unstable, or we will not fix this in 3.4.
--- End Message ---