Hi Javor On Sun, 2008-06-29 at 14:21 +0300, Javor Nikolov wrote: > 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?
As Oliver mentioned, it doesn't. > 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) - I doubt this is the case. Because Integration.pm:process_activity_commit has been written to first apply the comment and then attempt to change the status. Are you *sure* the bug was not FIXED when you tried to commit with this log message ? > (Why do I get the last error message printed twice also seems strange). That's a known bug that should be fixed in the next release. > 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 What do you mean by "presence_of_bug_ids doesn't make a difference" ? What was your complete log message when you tried both with this policy set to required and optional ? What you have described in (1) and (2) so far does not indicate a log comment.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
