Hello, I am an SA maintaining trac instances for several groups on the same web server. One of the groups is evaluating the agilo plugin.
I could not find any references to the problem I describe below on this group or with general Google searches. If anyone has heard of anything similar, please let me know. As long as the behavior below exists, I can't recommend deploying the agilo plugin. We are running several independent trac instances using trac-0.11.3 built in python 2.6 on openSuse 11.1 under apache2-2.2.10. (These are rpms either from the openSuse distribution or from the openSuse build service.) We are testing agilo-0.9.2 in a new test trac instance. I built this plugin from src against python 2.6 on the same machine where trac is installed. In the test trac instance, the agilo behavior seemed normal during several days of testing. Then it began failing with a syntax error in the trac.ini file. The end of the file contained an extra blank line and a line with only the text "se" on it, which was pretty obviously the syntax error. After cleaning that up, the test trac instance worked again, but I watched what was happening. With _every_ click on the web interface to the test trac instance, the trac.ini file was getting updated. What appears to be happening is that the templates_dir setting was getting overwritten. And the path that it was using was getting based in the other independent trac instances. For example, say I have three trac instances, testbed (with agilo installed), pm, and libre. After installation of agilo, the templates_dir line in the testbed trac.ini is: templates_dir = /srv/trac/testbed/.egg-cache/agilo-0.9.2-py2.6.egg-tmp/ agilo/templates After clicking on anything in the testbed web interface, I see this get rewritten as: templates_dir = /srv/trac/libre/.egg-cache/agilo-0.9.2-py2.6.egg-tmp/ agilo/templates The next click it might end up as: templates_dir = /srv/trac/pm/.egg-cache/agilo-0.9.2-py2.6.egg-tmp/ agilo/templates The only differences are in the trac instance name, testbed, libre, or pm. Sometimes it selects the testbed instance as well. Neither the libre nor the pm trac instances have ever had the agilo plugin enabled. Restarting the apache web server will generally stop this behavior for a while, but it comes back within a few minutes of using the testbed interface. I have not been able to determine whether there is some specific action which triggers the behavior. The corruption of the trac.ini file has only happened one time which lead me to discover this strange behavior. But I worry about it coming back with the trac.ini file being changed so frequently. Thanks for any pointers you might give me. Anthony Veale -- Follow Agilo on Twitter: http://twitter.com/agiloforscrum Please support us by reviewing and voting on: http://userstories.com/products/8-agilo-for-scrum http://ohloh.net/p/agilo-scrum http://freshmeat.net/projects/agiloforscrum You have received this message because you are subscribed to the "Agilo for Scrum" Google Group. This group is focused on supporting Agilo for Scrum users and is moderated by Agilo Software GmbH <http://www.agiloforscrum.com>. To post to this group, send email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo
