Kristis,
I'm afraid there's no change...
** Scmbug error 7: Resolving bug '166' from state 'assigned' to state
'resolved' would violate the workflow of the bug-tracker. Instead,
the resolution state could be changed to 'feedback' or 'resolved' or
'closed' states.
I tried the following restart approaches in order to be sure...
1/ service scmbug-server stop; service scmbug-server start
2/ kill `ps ax | grep scm`; service scmbug-server start
3/ complete o/s reboot
Any other suggestions?
- Andrew
On 2 Oct 2007, at 18:57, Kristis Makris wrote:
On Tue, 2007-10-02 at 08:44 +0100, Andrew Sykes wrote:
Kristis,
As a java person, this is not really my world, but I have tried the
patch (or at least applied the change) using the following steps...
1/ vi /usr/share/scmbug/lib/Scmbug/Daemon/Bugtracker.pm
2/ (change the variable name as indicated in viewcvs.)
3/ service scmbug-server restart
Try completely stopping the server. Making sure, 100% sure, absolutely
pretty sure that the server is not running. That the server process in
not running. Reboot if you have to. There have been reports that
restarting the daemon does not always work.
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
