Re: web/3044: Gnatsweb no longer working without Javascript

Re: web/3044: Gnatsweb no longer working without Javascript

[Phil Edwards]

The following reply was made to PR web/3044; it has been noted by GNATS.

From: Phil Edwards <pedwards@disaster.jaj.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gerald@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: web/3044: Gnatsweb no longer working without Javascript
Date: Fri, 8 Jun 2001 15:39:08 -0400

 On Fri, Jun 08, 2001 at 02:16:01AM -0000, Mark Mitchell wrote:
 >  >>>>> "Phil" == Phil Edwards <pedwards@disaster.jaj.com> writes:
 >  
 >      Phil> Phil P.S.- Anybody else think that high-priority PRs should
 >      Phil> be disallowed altogether during initial submission?  That a
 >  
 >  Yes -- but I don't know how to do that.
 
 For the record only:  complete guesswork, utterly untested (how could I test
 it?) patch against stock GNATS 1.113 sources follows.  One of these years
 there'll be enough time to persue this option with the gnats developers...
 
 String comparison tests written in decreasing order of likelihood, the
 idea is to fail as quickly as possible.
 
 
 --- pr.c.orig   Tue Mar  2 19:18:54 1999
 +++ pr.c        Wed Feb 28 16:37:48 2001
 @@ -747,6 +747,16 @@
           if (verify_enum (i, pr[i].value, token))
             found = TRUE;
 
 +         /* This hack prohibits random net submitters from submitting
 +             a high-priority PR; the idea is that maintainers should be
 +             the only ones permitted to raise priority to high.
 +             This should be more configurable. */
 +         if (found == TRUE && (!strcmp(pr[i].name,PRIORITY_STRING))
 +                            && (!strcmp(pr[i].value,"high"))
 +                            && (!strcmp(field_value(SUBMITTER),
 +                                        pr[SUBMITTER].default_value)))
 +           found = FALSE;
 +
           if (found == FALSE)
             {
               if (check)
 

Re: web/3044: Gnatsweb no longer working without Javascript

[Mark Mitchell]

The following reply was made to PR web/3044; it has been noted by GNATS.

From: Mark Mitchell <mark@codesourcery.com>
To: pedwards@disaster.jaj.com
Cc: gerald@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org,
        jsm28@cam.ac.uk
Subject: Re: web/3044: Gnatsweb no longer working without Javascript
Date: Thu, 07 Jun 2001 19:13:47 -0700

 >>>>> "Phil" == Phil Edwards <pedwards@disaster.jaj.com> writes:
 
     Phil> Phil P.S.- Anybody else think that high-priority PRs should
     Phil> be disallowed altogether during initial submission?  That a
 
 Yes -- but I don't know how to do that.
 
 --
 Mark Mitchell                   mark@codesourcery.com
 CodeSourcery, LLC               http://www.codesourcery.com

Re: web/3044: Gnatsweb no longer working without Javascript

[Phil Edwards]

The following reply was made to PR web/3044; it has been noted by GNATS.

From: Phil Edwards <pedwards@disaster.jaj.com>
To: gerald@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, jsm28@cam.ac.uk
Subject: Re: web/3044: Gnatsweb no longer working without Javascript
Date: Thu, 7 Jun 2001 15:05:47 -0400

 On Thu, Jun 07, 2001 at 11:42:57AM -0000, gerald@gcc.gnu.org wrote:
 > State-Changed-Why:
 >     Fixed, properly (instead of the original workaround), by
 >     upgrading to gnatsweb 2.8.1.
 
 I'll just pause to note that after submitting a change to a PR, I see
 "warning: refresh URL is not absolute" from the browser I use for gnats.
 Everything still works, though.
 
 
 Phil
 P.S.- Anybody else think that high-priority PRs should be disallowed
 altogether during initial submission?  That a PR should have to be /changed/
 to be high?  Just a pet peeve of mine...
 
 -- 
 pedwards at disaster dot jaj dot com  |  pme at sources dot redhat dot com
 devphil at several other less interesting addresses in various dot domains
 The gods do not protect fools.  Fools are protected by more capable fools.

Re: web/3044: Gnatsweb no longer working without Javascript

[gerald]

Synopsis: Gnatsweb no longer working without Javascript

State-Changed-From-To: analyzed->closed
State-Changed-By: gerald
State-Changed-When: Thu Jun  7 04:42:56 2001
State-Changed-Why:
    Fixed, properly (instead of the original workaround), by
    upgrading to gnatsweb 2.8.1.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3044&database=gcc

web/3044: Gnatsweb no longer working without Javascript

[Joseph Myers]

>Number:         3044
>Category:       web
>Synopsis:       Gnatsweb no longer working without Javascript
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    gerald
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jun 03 17:16:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Joseph S. Myers
>Release:        3.0 20010603 (prerelease)
>Organization:
none
>Environment:
System: Linux digraph 2.2.19 #1 Wed Mar 28 16:01:38 UTC 2001 i686 unknown
Architecture: i686

	
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-3cvs/configure --prefix=/opt/gcc/snapshot --disable-shared --enable-threads=posix --with-system-zlib
>Description:

As noted on overseers: gnatsweb is no longer working without
Javascript, whereas a few days ago it worked fine without Javascript
and after a fashion with lynx.  This is a highly inopportune time to
break GNATS.

>How-To-Repeat:

Try to use gnatsweb without Javascript.  Find that the "query" and
"advanced query" buttons do nothing.

>Fix:

Revert gnatsweb.pl to a working version if this can't be fixed
quickly.
>Release-Note:
>Audit-Trail:
>Unformatted: