Hi all, Last night I got tired of waiting for Fedora to release a 0.11 RPM so I installed trac manually. I am using the new WSGI interface and installed it with easy_install. I already ran into the (dunno-who-to-blame's) bug where Apache SetEnv for PYTHON_EGG_CACHE was being ignored unless I installed an unzipped copy of Genshi. 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.
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 of http://trac.edgewall.org/browser/trunk/contrib/trac-post-commit-hook shows it didn't change in 15 months, so that should be OK, not sure tho. Thanks! Aaron --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
