After the migration to new cl.net, Subversion commit mails were broken. Today, I fixed the issue (all links were pointing to a subversion location in /usr/local which didn't get ported over).
The links have been changed to all point to /custom/bin/svn-post-{commit,revprop-change}
Additionally, I've created a 'mailer.py' configuration file in /custom/conf/svn-mailer.conf which contains all the configuration to work with current and future repositories as long as they are being set up in the /project hierarchy.
In the armedbear project, I've long maintained a custom post-commit hookscript which invoked Trac's post-commit script to close or update tickets. This functionality has now been built into the default script, if there is a 'trac' directory residing next to the 'svn' directory within the project.
Bye,
Erik.
On Sat, Jun 4, 2011 at 11:41 PM, Erik Huelsmann ehuels@gmail.com wrote:
After the migration to new cl.net, Subversion commit mails were broken. Today, I fixed the issue (all links were pointing to a subversion location in /usr/local which didn't get ported over).
The links have been changed to all point to /custom/bin/svn-post-{commit,revprop-change}
Additionally, I've created a 'mailer.py' configuration file in /custom/conf/svn-mailer.conf which contains all the configuration to work with current and future repositories as long as they are being set up in the /project hierarchy.
In the armedbear project, I've long maintained a custom post-commit hookscript which invoked Trac's post-commit script to close or update tickets. This functionality has now been built into the default script, if there is a 'trac' directory residing next to the 'svn' directory within the project.
To learn more about the kind of "commands" the trac post-commit integration supports, read http://trac.edgewall.org/browser//tags/trac-0.11.7/contrib/trac-post-commit-...
Bye,
Erik.
-
Erik Huelsmann