What is this ?

[Dirk Schenkewitz]

Hi People,

First, I'm using gnats-3.999.1 and a version of gnatsweb which
contains:

# $Id: gnatsweb.pl,v 1.87 2001/12/12 14:10:56 yngves Exp $

After some time, my boss said, it would be nice to have most
of all changes to a PR logged and to require reason-for-changes
for certain fields. So I added:

 on-change {
    # When the field is edited, we want an audit-trail entry to be added,
    add-audit-trail
    # ... and we want to require a reason for the change.
    require-change-reason
  }

to the following fields:
Category, Synopsis, Confidential, Severity, Priority, Class,
Submitter-Id, Originator, Description, How-To-Repeat
and

 on-change {
    # When the field is edited, we want an audit-trail entry to be added,
    add-audit-trail
  }

to some further fields. Now, when I edit a PR, it happens that gnats
does not accept what was sent. (The change is e.g.: "State" from "open"
to "pre-anylyzed" and a "." in the "Reason Changed"-area following
"State".) Gnatsweb always comes up with the message:

 Error

 Field 'How-To-Repeat' must have a reason for change

even though I did not edit the 'How-To-Repeat'-field anyhow. When
I put a single dot in the "Reason Changed"-Area following "How-To-
Repeat", I get the message:

  Error

  Return code: 403 - Edit of field Description requires a change reason.

  Return code: 450 - Failed writing out PR.

Putting a dot into the "Reason Changed"-Area following "File attachments"
does not help. Putting dots in all visible "Reason Changed"-Areas also
does not help, the same message comes back, over and over. (Btw, there is
no "Reason Changed"-Area displayed between "Description" and "File attach-
ments".) And another strange thing is that this dos not always occur -
some PRs can be edited, others not.

After some fiddling around I managed to get this mail:
-----------------------------------------------------------------------
From: address@hidden
To: gnats-admin
Reply-To: bugs
Subject: Re: Test-Gnats/3341

Synopsis: only for test

State-Changed-From-To: open->pre-analyzed
State-Changed-By: ds
State-Changed-When: Fri, 04 Oct 2002 18:57:26 +0200
State-Changed-Why:
just curious



Betriebssystem-Changed-From-To: ->?
Betriebssystem-Changed-By: ds
Betriebssystem-Changed-When: Fri, 04 Oct 2002 18:57:26 +0200
Betriebssystem-Changed-Why:


Environment-Changed-From-To: ->

Environment-Changed-By: ds
Environment-Changed-When: Fri, 04 Oct 2002 18:57:26 +0200
Environment-Changed-Why:


Fix-Changed-From-To: ->

Fix-Changed-By: ds
Fix-Changed-When: Fri, 04 Oct 2002 18:57:26 +0200
Fix-Changed-Why:


Release-Note-Changed-From-To: ->

Release-Note-Changed-By: ds
Release-Note-Changed-When: Fri, 04 Oct 2002 18:57:26 +0200
Release-Note-Changed-Why:


Unformatted-Changed-From-To:  
-> 
 

Unformatted-Changed-By: ds
Unformatted-Changed-When: Fri, 04 Oct 2002 18:57:26 +0200
Unformatted-Changed-Why:


-----------------------------------------------------------------------

All I really changed in this PR is described by:

State-Changed-From-To: open->pre-analyzed
State-Changed-By: ds
State-Changed-When: Fri, 04 Oct 2002 18:57:26 +0200
State-Changed-Why:
just curious


Now, this looks to me as if gnatsweb creates some (empty?) changes
on its own, accompanied with (empty?) "Changed-Why"-fields, which in
turn cause gnats to sometimes reject the whole thing. (In this case
it accepted it.) Can this be true? I doubt.

Well, can anybody help me with this problem ?
Or even see & tell me what's going on ?

(Another thing: I had some difficulties with debugging - forgive
me the silly question: What do I have to do if I want to see what
gnatsweb intends to send to gnats, especially after hitting
"submit edit" ?)

thanks in advance
        dirk

-- 
Dirk Schenkewitz 

InterFace AG                 fon: +49 (0)89 / 610 49 - 126
Leipziger Str. 16            fax: +49 (0)89 / 610 49 - 83
D-82008 Unterhaching         
http://www.interface-ag.de   mailto:address@hidden