Your message dated Sat, 18 Jun 2016 00:52:54 +0200 with message-id <[email protected]> and subject line closing bugs reported against ancient GCC versions has caused the Debian Bug report #500527, regarding contradictory GCC bug reporting instructions 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.) -- 500527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500527 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gcc-4.3 Version: 4.3.2-1 /usr/share/doc/gcc-4.3/README.Bugs says: There are complete instructions in the gcc info manual (found in the gcc-doc package), section Bugs. The gcc info manual in gcc-doc (version 5:2), in that section, has a list of criteria for reporting bugs, but then the section titled "How and where to Report Bugs" contains only one sentence: Bugs should be reported to the bug database at http://bugs.debian.org/. If these are indeed the complete instructions, then I would suggest that they be inserted directly into README.Bugs instead of forwarding the reader to the Info manual. It also seems odd that the "Summarized bug reporting instructions" later on in README.Bugs are much longer than the "complete" bug reporting instructions given in the info manual. I think that something must be missing. -- Ben Pfaff http://benpfaff.org
--- End Message ---
--- Begin Message ---This bug has been reported against an ancient version of gpc (4.1), gcc/g++/gfortran (4.3), or gcj/gij/gobjc (4.4), that was last released with Debian 6.0 (squeeze). But even squeeze-lts has now reached end-of-life and is no longer supported. The bug is assumed to be fixed (or no longer relevant) in newer GCC releases and therefore I'm closing this report now. If the problem is still reproducible in the currently supported versions (gcc-5, gcc-6 or corresponding g++/gcj), feel free to provide more information, reopen and reassign this bug report. Andreas
--- End Message ---
