On Wed, 2008-02-06 at 11:24 +0530, manjit wrote: > I'm able to commit after changing the version number. But still the old > problem persists. I don’t any see the log comments updated in the Bugzilla. > I really doubt if scmbug is interacting with the db properly. Is there any > way to find out what it is doing with the db? I am kinda really frustrated > after spending so much time to make it up and running.
Manjit I understand that you are frustrated. Now that you have changed back to 2.22.x, can you try changing the product name in glue.conf to an invalid product name, and then trying to commit ? If you get an error from Scmbug saying that the product name is invalid for the bug number you specified, then indeed the Scmbug daemon is talking to the database properly. If this works, then you will need to apply modifications to the daemon as I've described before in a previous email (writing *YOUR OWN* logging statements to /tmp/debuglog) and try *YOURSELF* to figure out where the Scmbug daemon stops responding. You need to help out here. I can't do this debugging for you. I'm sorry for the state of things, but this is what needs to happen to find out what the daemon is doing.
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
