Hi again,

Apologies for responding to my own post.  A couple more points:

1. I have disabled the user mapping because my subversion and bugzilla
logins are the same (they both auth against ldap).

2. I now get this error message on the daemon activity log:

==> /var/log/scmbug/activity.log <==
Tue Mar 27 10:14:29 2007 10.147.26.81:49906 Processing connection from
Tue Mar 27 10:14:29 2007 10.147.26.81:49906 Processing an
'activity_commit' for bug id '3305' from SCM user 't25125'
Tue Mar 27 10:14:29 2007 10.147.26.81:49906 The changeset comment
could not be added. This must be due to a bug in the bug-tracker
backend.
Tue Mar 27 10:14:29 2007 10.147.26.81:49906 Connection from  processed
Tue Mar 27 10:14:29 2007 reaped 23036

How do I debug this further?  This is against bugzilla 2.20.

cheers,
dim

On 3/27/07, Dmitri Colebatch <[EMAIL PROTECTED]> wrote:
Hi all,

Please excuse the general question.... I have tried to glean what I
can from the docs but am a little confused why my setup isn't working
as I'm expecting.  I have bugzilla on one machine (toyibusdf2) and
subversion on another (svn).  I have configured the daemon on
toyibusdf2 and have it running against bugzilla 2.20 using LDAP
userlist mapping.  On the subversion machine I have run the glue
install script:

scmbug_install_glue --daemon=toyibusdf2 --scm=Subversion
--repository==file:///home/subversion/svn_repository --bug=3302
--product="Dev Env" --binary=paths=/bin,/usr/bin

But am not having much joy.  I've further tweaked the config by making
the following changes:

       presence_of_bug_ids =>  {
           value => 'optional'
           },

       minimum_log_message_size => {
           enabled => 0,
           size => 50
           },

       valid_product_name => {
           enabled => 0,
           type => 'manual',
           value => 'Dev Env'
           },

The rest of the
/home/subversion/svn_repository/hooks/etc/scmbug/glue.conf file is as
the script created it.

I've created a test bug in bugzilla and have tried to commit a change like so:

 svn commit -m "bug 3305: removed token change" test.txt

However I don't see anything show up in bug 3305, nor do I see
anything in the daemon logs.  Where should I start looking for
details?

My second question is related to the product name.  I don't understand
why its required.  We have one repository and one bugzilla instance.
I want to configure this so that each commit to subversion that
contains "bug xxxx: blah blah" will have the corresponding comment
added to the bug (as per
http://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-19-9/manual/html-multi/x202.html).
 Given that bug id is the key, I don't want to have to specify the
product at all - can someone explain why it is required?

Thanks again for your help.

cheers,
dim

ps - The scmbug_install_glue script doesn't like being given binary
paths as /usr/bin,/bin (instead of /bin,/usr/bin).  It complains about
not being able to find diff, which is at /usr/bin/diff.

--daemon=toyibusdf2 --scm=Subversion
--repository==file:///home/subversion/svn_repository --bug=3302
--product="Dev Env" --binary=paths=/bin,/usr/bin

_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users

Reply via email to