Got some more info. I have been putting that debug statement in various places in the SCM.pm file. Here are some snippets(like the log message?),
$VAR1 = bless( {
'repository' => 'd:\\repos/research',
'original_log_message' => 'AHHHHHHHHHHHHHHHH
Issue: 659
',
'files' => {
'test.txt' => {
'new_version' => '107',
'old_version' => 'N/A'
}
},
'user' => 'Me',
'name' => 'activity_verify',
'product_name' => 'Archive_Product'
}, 'Scmbug::Activity' );
Here is what appears in the log from TortoiseSVN Bugtraq, Issue: 659
Here are my regualar expressions from the glue.conf,
bugid_regex => '.*Issue:\s*(.*?)$',
bugid_split_regex => ',\s+#|\s+#|,|\s+',
log_regex => '^(([^\r\n]|[\r\n])*)Issue:.*$'
I have also attached my config files.
Again , thanks in advance,
Tony
-----Original Message-----
From: Day, Tony
Sent: Wednesday, April 18, 2007 8:45 AM
To: 'Kristis Makris'; [EMAIL PROTECTED]
Cc: [email protected]
Subject: RE: [scmbug-users] Bugzilla Not Being Updated
A little progress. I tried your suggestions and set to threaded and forked to
no avail. Then I rec'd Thorstens e-mail. He suggested it was something with
my regular expression so I redid it...for like the 10th time :)
I had been using the example from here,
http://blog.platinumsolutions.com/node/102 Interestingly, I ran into something
else I had not run into before. I was copying and pasting the regular
expressions from the blog into my glue.conf file and this morning I noticed
something. The blog has front and back ticks for the single quotes. SCMBug
did not like that. I changed the front and back ticks to be single quotes "'"
and that problem was solved.
So good news, I now have this in the activity log,
Wed Apr 18 08:01:11 2007 xxx.xxx.xxx.xxx:xxxx Processing an 'activity_verify'
for bug id '659' from SCM user 'me'
Wed Apr 18 08:01:11 2007 xxx.xxx.xxx.xxx:xxxx Connection from ‰íÐ processed
Bad news is that the bug is still not being updated. Then I came across this,
http://www.mail-archive.com/[email protected]/msg00231.html
Changed my append to be true as well but still no luck. But, I also have a
space in my product name as the above link described. I have tried double
quotes but still nothing is being updated in the bug. So I changed my product
to contain an underscore instead of a space. Tried single and double quotes.
Still nothing.
Kristis, in the second link I provided above you suggested putting some debug
code into scm.pm file to see how the message is actually being interpreted. I
will give that a shot and see what I get. If that does not help, I will post
my glue.conf and daemon.conf files for everyone.
Thanks to all for your suggestions,
Tony
-----Original Message-----
From: Kristis Makris [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 17, 2007 4:44 PM
To: Day, Tony; [EMAIL PROTECTED]
Cc: [email protected]
Subject: Re: [scmbug-users] Bugzilla Not Being Updated
Hi Tony,
It looks like you are having a really hard time to get the system
working. This REALLY concerns me. Given your quite thorough efforts I'm
becoming convinced that you must be hitting some environmental error
that's beside our reach. The first thing that comes to mind are the
problems some people have been having with a version of the daemon that
works in fork mode under Windows. Could you please manually switch the
daemon configuration to "threaded" mode retest, and then "forked" and
retest ? I'm worried that this might be a DBI or ActiveState Perl issue
and I want to make sure you try both these options -- they were
developed to address this issue.
The current daemon configuration is probably "auto" which under your
Windows configuration must have automatically switched to "threaded",
but please try both configurations anyway:
http://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-19-9/manual/html-single/manual.html#INSTALLATION-INTEGRATION-DAEMON
It looks like problems with Bugzilla 2.22 on Windows were reported
before by David:
http://bugzilla.mkgnu.net/show_bug.cgi?id=912
http://lists.mkgnu.net/pipermail/scmbug-users/2007-March/000852.html
David, did you end up trying 0.19.9 at all ? What happened in your
case ? Did the upgrade to Bugzilla 2.22.2 help ? Was this a daemon issue
that was fixed in 0.19.9 ?
On Tue, 2007-04-17 at 15:18 -0600, Day, Tony wrote:
> Hello all,
>
> I've been pulling my hair out for the last two days trying to get this
> working and I am stuck.
>
> I have Subversion 1.4.3 on a Windows Server 2003 machine
> I have Bugzilla 2.22.0 on a Windows Server 2003 machine
> I am using SCMBug version 0-19-9
>
> Try as I might, I cannot get SCMBug to update the bug. It's extremely
> hard to debug when all I get in the activity log is:
>
> Tue Apr 17 14:23:08 2007 XXX.XXX.XXX.XXXX:XXXX Processing connection
> from ‰íÐ
> Tue Apr 17 14:23:08 2007 XXX.XXX.XXX.XXXX:XXXX Connection from ‰íÐ
> processed
According to this, the connection went through. I'd recommend you start
debugging in the Bugzilla backend in Bugzilla.pm:integration_add_comment
to see what goes wrong.
> On a sidenote, anyone know why I get weird characters that should be
> specifying the server in the log?
Yes.
http://bugzilla.mkgnu.net/show_bug.cgi?id=264#c35
http://bugzilla.mkgnu.net/show_bug.cgi?id=264#c30
> From what I can tell the glue.conf is okay. I have verified the daemon
> location and port are okay. I've tried various log templates to no
> avail. My main_trunk_directory is called LAG. While that shouldn't
> matter I feel I should mention it as I am not using the 'recommended'
> dir name.
It should be easy to test a new repository with a main_trunk_directory
called 'trunk' though. I doubt this is the problem. Thanks though.
> Far as I can tell the daemon config is okay too. I have tried auto
> and threaded execution modes. I verified that I correctly input the
Could you try both 'forked' and 'threaded' again please ? Are you sure
you are restarting the daemon each time ?
> bugtracker type,version,location and port. For the port I tried
> localhost, 127.0.0.1, and the IP of the machine. No joy. I verified
> the database name, username, and password are accurate. I used the
> one-to-one mapping for SCM usernames. I know that is right cause if I
> put in something SCMBug doesn't like I get an error when trying to
> commit to SVN.
>
> At this point, I really hope I am just overlooking something obvious
> and stupid cause I've wasted two days trying to get this running. If
> there is any additional information I can provide please let me know.
If it's not the forked vs threaded issue, I think you might have to
resort to debugging the Bugzilla backend.
I know this isn't exactly the answer you were expecting.
daemon.conf
Description: daemon.conf
glue.conf
Description: glue.conf
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
