Kristis,
Thanks, I'll probably try some stuff tonight.
First I'm going to upgrade Bugzilla from 2.22 to 2.22.2 (there are at
least two bugs in 2.22 that I've run in to) and then if that
doesn't fix it then I'll try upgrading SCMBUG and see if that fixes it.
I'll report back.
- David
Kristis Makris wrote:
Hi Uri,
On Wed, 2007-02-21 at 11:00 +0200, Uri Shohet wrote:
The thing is, I didn't know what product name to specify, since we have many
products in Subversion and the repository looks like this:
Product1
branches
tags
trunk
Product2
branches
tags
trunk
...
and so on. So I've configured valid_product_name like this:
valid_product_name => {
enabled => 0,
type => 'auto',
value => '(.+?)/'
}
That's great. It's the right thing to do.
The problem now is that I can commit to Subversion, but when I write comments
like "bug 1234:long comment", I get an email from me and Scmbug Owner to all
the people registered in the bug, with Subject like "[Product1][Bug 1234]:
Bug summary", but no comment is being added to the Bug in Bugzilla. It did
work before the upgrade.
The daemon is certainly being contacted with the glue. How can the
comment not be added ? My gut feeling is that you are running a 2.22
Bugzilla. Did you upgrade Bugzilla at all ?
What am I missing?
This scares me. Are you sure MySQL is running ? Are you sure the daemon
has been restarted ? Is there anything
in /var/log/scmbug/{activity,error}.log ? What version of Bugzilla are
you running ? Version 0.19.7 works for me with Bugzilla 2.20.1, but I
know there have been some problems with 2.22 in Windows:
http://bugzilla.mkgnu.net/show_bug.cgi?id=912
Perhaps the problem isn't just on Windows ?
By the way, David: Can you try 0.19.9 ? The threaded version of the
daemon for Windows might fix this problem.
Also, Uri, could you try 0.19.9 in both the forked and theraded modes ?
Just keep in mind that with the theraded mode in Linux you might get a
slowdown. I'm actually curious to see if you do. I get some in Debian
3.1.
http://bugzilla.mkgnu.net/show_bug.cgi?id=264#c7
The last resort I have is for you to start adding debugging statements
to see what's going on. This is strange.
_______________________________________________
scmbug-users mailing list
scmbug-users@lists.mkgnu.net
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
