Hi eGore, I think this is a bug:
http://bugzilla.mkgnu.net/show_bug.cgi?id=1055 and that it most likely depends on changes to http://bugzilla.mkgnu.net/show_bug.cgi?id=1050 On Wed, 2007-10-24 at 10:33 +0200, eGore wrote: > I'm trying to set a bug to RESOLVED FIXED when I commit something. I used the > commit comment: > > bug 1234: do this do that > status 1234: resolved fixed > > This brought up the error: > Scmbug error 7: Resolving bug '1234' from state 'ASSIGNED' to state > 'resolved' would violate the workflow of the bug-tracker. Instead, the > resolution state could be changed to 'RESOLVED' state. > > So I think the check does not work case insensitive (which is not intuitive). > But I changed my message to: That's a good observation. This feature should be added: http://bugzilla.mkgnu.net/show_bug.cgi?id=1056 > bug 1234: do this do that > status 1234: RESOLVED FIXED > > This brought up the error: > Scmbug error 7: Invalid resolution 'FIXED' when resolving bug '1234' from > state 'ASSIGNED' to state 'RESOLVED'. Instead, a valid resolution could be . Bugzilla.pm.in:integration_valid_resolutions_list should have at least returned a list of valid resolutions. It seems that integration_bug_resolution_change_is_valid is returning with an error, which later leets to the call to integration_valid_resolutions_list. > So I think it scmbug does not know of the different RESOLVED states. That's not true. The Bugzilla backend has these defined in variable $bug_status_map.
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
