Ya, you are absolutely right, it never gets to Bugzilla. I put some debug statements the Bugzilla.pm earlier. Also, I had already put some bad data in yesterday to see how far through the verify it got. I put in some bad syntax for the user translation and I got the expected error. I will put some more debug statements in daemon.pm and see what I can find.
Thanks! -----Original Message----- From: Kristis Makris [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 18, 2007 11:03 AM To: Day, Tony Cc: [email protected] Subject: RE: [scmbug-users] Bugzilla Not Being Updated 'original_log_message' => 'AHHHHHHHHHHHHHHHH > Issue: 659 > > ', Well, the original_log_message seems backwards. "Issue" should be before the log message. On Wed, 2007-04-18 at 09:42 -0600, Day, Tony wrote: > Wed Apr 18 08:01:11 2007 xxx.xxx.xxx.xxx:xxxx Processing an 'activity_verify' for bug id '659' from SCM user 'me' Clearly, the daemon is being contacted. Do you see a similar statement for "Processing an 'activity_commit'" ?? If you see one, then the daemon is contacted again to insert the comment in the bugtracker. If not, then perhaps the hook is not triggering on a commit (in post-commit.bat). Also, can you try something that is clearly incorrect ? e.g. Change the product name in glue.conf to "something_invalid" and try to commit. The commit should be refused. If it's not, perhaps when activity_verify is issued the daemon is not talking to the database correctly. My gut feeling is that the daemon is not talking to the database. Could you add debug statements in Bugzilla.pm:integration_add_comment() ? I bet you would never see them. _______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
