Kristis, Very sorry I didn't get back to your last email, it landed in the middle of a holiday week for me, so it never quite made it to the top of the todo list.
I'm afraid your last suggestion was a step to far for me, we're pretty reliant on the Mantis system, so I really can't start trying out patches against it. Even though I could roughly see where you were going with it. Perhaps when things calm down a bit I'll return to this, or when we upgrade Mantis, the problem might go away, but in the meantime, most of scmbug is working fine and has definitely helped the development process. Thanks again for all your help, and for a pretty cool tool! Andrew Sykes Open Equal Ltd t: 07966 551 998 e: [EMAIL PROTECTED] ----- Original Message ----- From: "Kristis Makris" <[EMAIL PROTECTED]> To: "Andrew Sykes" <[EMAIL PROTECTED]> Cc: [email protected] Sent: Monday, October 15, 2007 8:14:44 PM (GMT) Europe/London Subject: Re: [scmbug-users] status command problems Andrew, have you tried my last recommendation ? What was the outcome ? On Tue, 2007-10-02 at 22:42 +0200, Andrew Sykes wrote: > 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
