Hi,

I did some more detailed tests on a different (test) environment.  And
now I discovered I wasn't precise when I described the problem - it's
not the case of the resolution status which matters, it's the "status"
keyword itself. resolution_status_case_sensitive_verification => 0
should also apply to it, doesn't it?
Example:
1) Lower-case status
status 6: RESOLVED FIXED
that works fine and changes the status to resovled fixed. And the
"status 6: RESOLVED FIXED" text is not being logged as part of
bugzilla comment body.

2) Mixed-case status
Status 6: RESOLVED FIXED
This text "Status 6: RESOLVED FIXED" remains part of bugzilla comment
body and the bug status is not changed. However, as I mentioned before
- the same expression is anyway recognized as attempt to change bug
status since when applied to an already fixed bug (or new one) -
verification fails like that:

svn commit -F svn-commit.tmp
Sending        test.txt
Transmitting file data .svn: Commit failed (details follow):
svn: MERGE request failed on '/svnrepos/demorep1/demoproject1/trunk'
svn: 'pre-commit' hook failed with error output:
Scmbug notice: ---------------------------------------------------------
Scmbug notice: Preparing for VERIFICATION
Scmbug notice: Processing activity
Scmbug notice: Submitting request
Scmbug notice: Request submission was denied
Scmbug ERROR> Connection.pm:370 -
*******************************************
**
**
** Scmbug error 7: Bug '6' is in the 'RESOLVED' state, instead of the
'ASSIGNED' or 'REOPENED' states.
**
**
*******************************************

*******************************************
**
**
** Scmbug error 7: Bug '6' is in the 'RESOLVED' state, instead of the
'ASSIGNED' or 'REOPENED' states.
**
**
*******************************************


(Why do I get the last error message printed twice also seems strange).

Seems that presence_of_bug_ids doesn't make a difference - I've tested
the above both with required and optional. All the other glue.conf
settings haven't been changed except mail_notification which anyway
doesn't apply to resolution statuses at all.


On Sat, Jun 28, 2008 at 3:43 PM, Kristis Makris <[EMAIL PROTECTED]> wrote:
> Hi Javor,
>
> This sounds like a bug to me.
>
> http://bugzilla.mkgnu.net/show_bug.cgi?id=1198
>
> I wonder if it's a variation of
>
> http://bugzilla.mkgnu.net/show_bug.cgi?id=1124
>
>
> On Sat, 2008-06-28 at 11:53 +0300, Javor Nikolov wrote:
>> We haven't tested this behaviour very thoroughly and I'm not sure if
>> it allways reproduces. Is it the way it should work and if not - is
>
> Perhaps you could test it again to be sure ?
>
>> there anyone else with the same problem (or there is something wrongin
>> our setup)?
>
> I doubt this is a setup problem, assuming you haven't modified the
> configuration options in glue.conf, policy resolution_template.
>
>
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users

Reply via email to