Kristis,
I did that. Initially it wouldn't create the log file. That was how we
found the problem in the batch files. After that it was a matter of
tweaking Bugzilla.
*Martin Goff*
Software Development Alternatives, Inc.
[email protected] <mailto:[email protected]>
928-632-9946 (work)
928-632-9943 (fax)
"Effective teaching is the essence of leadership..."
Kristis Makris wrote:
Hi Martin, it sounds like you are running into a lot of trouble. This
shouldn't be so hard to setup. I'm wondering if there is some major
problem here we weren't aware of.
Can you enable logging to a file in glue.conf ? This is different than
the daemon log messages.
Essentially change 'logging' configuration to:
log4perl.category.Glue = DEBUG, AppWarn, AppRest, Logfile
#log4perl.category.Glue = WARN, AppWarn, AppRest
You should see a file C:\Temp\scmbug_glue.log show up when you try to
commit.
On Tue, 2009-07-28 at 12:02 -0700, Martin Goff wrote:
This is frustrating. I created a new SVN repository (named for the
client to whom it applies), dumped the data from the one named "repos"
and loaded it into the new repository.
Then I installed the glue, using the new repository name. It created
the glue files like I expected it would. I modified the glue.conf so
the commit message only has to be 10 chars and I updated the
log_bugid_regex and log_body_regex values so the Bug id would be
case-insensitive.
Now I'm back to TortoiseSVN generating error messages but the glue
activity log never gets created.
Commit blocked by pre-commit hook (exit code 1) with output:
The system cannot find the path specified.
What am I doing wrong?
Martin Goff
Software Development Alternatives, Inc.
[email protected]
928-632-9946 (work)
928-632-9943 (fax)
"Effective teaching is the essence of leadership..."
Kristis Makris wrote:
On Fri, 2009-07-24 at 16:38 -0700, Martin Goff wrote:
After I made this change I received another error:
Scmbug error 7: Bug '2'
Error: does not belong to the product 'repos'. It belongs to product 'VDLSim'.
Well, to be clear, you received this error when you tried to commit a
change in the repository against bug 2. Right ?
So, originally you had ran:
J:\ScmBug\bin>scmbug_install_glue.pl --scm=Subversion --product=repos
That ended up assuming that you have setup this repository to integrate
it with the Bugzilla product name "repos". You probably intented to
setup this repository to integrate it with the Bugzilla product
"VDLSim". So, the original glue configuration was incorrect.
You can tune in hooks/etc/scmbug/glue.conf the glue configuration. So if
you need to change the product name you can simply edit that file.
On Mon, 2009-07-27 at 13:21 -0700, Martin Goff wrote:
Are there any files that get updated when the glue is installed that
do not exist within the hooks directory tree?
Yes, there are files in /hooks that are the actual Subversion hooks.
Those did not exist, and the Scmbug glue installer created them to
enable the integration. Those are called "post-commit" and "pre-commit".
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
