On Fri, 2007-07-13 at 15:39 +0930, Maginnity, Simon (Contractor) wrote: > I was asked a few questions about my server setup, I assume this is so > that youc an replicate the problem, do you need to know anything else in > order to get this problem fixed, I cannot remember if I mentioned that I > am running under Suse Linux 10.1 > > Bugzilla 2.22 > Scmbug 19.13 > Suse Linux 10.1 > The glue/hooks are installed > > I enter a message in svn from a windows client and upload/change a file > anf log that against an assigned bug in bugzilla and the message I enter > does not come up in bugzilla under that bug or anywhere I can see in > bugzilla? > > What have I done wrong?
Thanks for the detailed environment description. You are running Scmbug on Linux. It has not been reported before that Scmbug would not work with Bugzilla 2.22. I wonder if your username/password/database configuration in glue.conf is correct. For example, can you connect to the mysql database using those credentials with the mysql client ? e.g. $ mysql -u username -ppassword databasename I know that we have poor error reporting related to database connectivity and perhaps you are not getting an indication that you are failing to connect to the database. Another test you could do is to commit using a bug number that does not exist, or a bug number that belongs to a different product. If the commit goes through this means the Scmbug daemon did not manage to connect to the database to verify the bug number. This could be another indication that this is a database problem.
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
