On Jul 18, 4:17 pm, "Aaron D. Marasco" <[EMAIL PROTECTED]>
wrote:
> I did all kinds of tests on trac and was happy with
> it. Installed the FullBlogPlugin and played with that a little; it's perfect
> for my weekly summations for my customer.
Yes, that sure is a nice plugin... ;-)
> This morning, when I tried to check in a file, TortoiseSVN said that the
> commit failed, but it failed with HTTP/200 OK "error." So it didn't fail.
> The trac post-commit hook must've ran, because the commit is in my
> Timeline/Source Browser. There are no errors that I can see in my httpd
> logs. But my local copy is now messed up because it thinks the commit
> failed, so hasn't updated the local files.
>
> Since the egg cache was an issue before, I tried adding:
> export PYTHON_EGG_CACHE='/var/www/.python-eggs/'
> to the post-commit script that calls trac-post-commit, but that didn't help.
> So I edited the trac-post-commit file itself and added:
> os.environ['PYTHON_EGG_CACHE']='/var/www/.python-eggs/'
> which also didn't help. But again, I think the script itself is running
> since the trac db gets an update.
>
> Has anybody seen anything like this? Any ideas where I can start looking
> for an actual error code? That machine is not online now so I can't do a
> diff, but a quick check
> ofhttp://trac.edgewall.org/browser/trunk/contrib/trac-post-commit-hookshows
> it didn't change in 15 months, so that should be OK, not sure tho.
>
I'm not sure what you are trying to do. The post-commit-hook is not at
all related to the Timeline/Browser for reading source and new
changesets - that access happens all through the python-subversion
bindings in code when requests to Trac are made.
That does not mean your script or installation does not have problems
of course. The script runs after a commit ('post'), so it will not
stop the commit from happening (as confirmed in the timeline). Also,
the 'HTTP/200 OK' is a web request status, and not I think directly
related to the status an individual post-commit hook.
Depending on setup, your Apache -> mod_svn -> post-commit-hook could
for instance be running in a different context from the mod_wsgi
process. If you remove the trac post-commit-hook, does your Tortoise/
Subversion setup work correctly? Do you have more than one Python
installed?
If things don't pan out, you need to do some logging and get more
details on the actual error that occurs.
:::simon
https://www.coderesort.com
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
