web/830: gnatsweb creates PRs with bogus version information
Joseph Myers
jsm28@cam.ac.uk
Fri Nov 17 03:46:00 GMT 2000
>Number: 830
>Category: web
>Synopsis: gnatsweb creates PRs with bogus version information
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: gerald
>State: open
>Class: accepts-illegal
>Submitter-Id: net
>Arrival-Date: Fri Nov 17 03:46:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator: Joseph S. Myers
>Release: 2.97 20001116 (experimental)
>Organization:
none
>Environment:
System: Linux decomino 2.2.17 #1 Mon Sep 4 20:22:16 UTC 2000 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-cvs/configure --prefix=/opt/gcc/snapshot --disable-shared --enable-threads=posix --with-system-zlib
>Description:
Some PRs appear to be entering GNATS with the GCC version
"unknown-1.0" listed - this seems to be the gnatsweb default version.
This version information is useless; gnatsweb should refuse to accept
PRs without a proper version.
>How-To-Repeat:
Observe PRs arriving on gcc-bugs with "unknown-1.0" as the only
indication of the version affected.
>Fix:
gnatsweb should insist that a proper version be given if "unknown-1.0"
is the version in a submitted PR.
(Ideally, it would also, if the version specified predates 2.95, tell
the user to test with a more current GCC first, but this probably
requires too much intelligence.)
(Also, gnats.html should recommend gccbug as preferred for submitting
bugs against snapshots/3.0, since gccbug now automatically includes
the full version, host/build/target and configure options. Similarly,
bugs.html should make it clear that it is preferred for bug reports to
go via GNATS rather than direct to gcc-bugs and that they're less
likely to be forgotten about if they go to GNATS.)
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the Gcc-bugs
mailing list