Hi all again:

Yes, I forgot a couple of details, sorry for that ... I'll put the
answers below ...

On 2/1/07, Matthew Gillen <[EMAIL PROTECTED]> wrote:
>
> Leandro Conde wrote:
> > Hi Trac people,
>
>> If the solution is to upgrade, I will proceed with that ... but, since
>> the post commit hook is external to Trac, seems that it has nothing to
>> do with this problem.

> But the hook script talks to the same database backend as Trac, so if there's
> a mismatch, it could cause trouble.

Yes, that's right ... I didn't check to see if there are a new version
of it, though ... Of course, I will do so now ...

>
> > The setup that I've choosed is one single svn repository with multiple
> > tracs 'seeing' portions of it.
>
> So which trac instance does the post-commit hook operate on?  All of them?
>

I've resolved this by setting a property (trac:project) in the SVN
which points me to the right Trac environment (only the name of it
since all of them are below the same root, a local path in the
server).

Then I made a simple CMD batch file (I didn't knew python programming
at the time, now I'm more confident of it, so, if I have the chance I
will rewrite it in python) which uses the svnlook command to get that
property value and then call the hook script with the right
parameters.

> > The SVN repository has grown a bit now, it has nearly 4000 revisions,
> > made mostly by importing stuff from another 'version control system'
> > (the one from M$).
>
> Once it's in the trac-post-commit-hook.py, it shouldn't need to interact with
> the subversion repo, so the size of the repo shouldn't matter.

Yes, thats right ... I'm using the pre-commit-hook also, and it didn't
have the same problem. Seems it has something to do with the part that
are modifying the ticket (refs or closes) or maybe the mail sending
stuff ... I haven't been able to test that issue properly, though ...

> > So, is this a known problem? It has any solution? Is there any other
> > hook script to try out?  Upgrading has any to do with it?
>

> How many tickets do you have in your ticket database?

It varies as it depends on the environment pointed at ... some of them
(the larger ones) have a couple hundreds tickets, but some others less
than a hundred.
I didn't see any delay variations depending on which environment I'm using ...

> What database are you using (sqlite is the default)?

Yes, I'm using SQLite ... Didn't have the time to change it since
install ...  Though I'm planning to upgrade to PostreSQL on Windows
when I have a chance ...

>
> Matt

Thank you Matt,

Kind regards,
Leandro.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to