[Cryptech Tech] Some problems with the repo access

[Rob Austein]

This turned out to be two separate problems.

1) Gitolite's use of its POST_CREATE trigger is, um, whimsical.
   If for some sick reason you really want to know what's going on
   here, see:

     http://gitolite.com/gitolite/triggers.html#trigger-specific-arguments-and-other-details

   I would advise against reading this (or, really, any of the
   Gitolite documentation) if you've eaten recently.

   Since the documentation makes it fairly clear that the trigger will
   do whatever amuses Gitolite's author this week, I changed the
   trigger script not to make any assumptions about the state of the
   binding between Trac and git when it is called.  The trigger script
   now always attempts to "resync" Trac with the repository, and, if
   that fails, attempts to "add" the repository to Trac.

   Note that there does not appear to be any trigger we can catch
   which will tell us about repository deletion, so deletions will
   require manual cleanup by a sysadmin.  With luck, we won't be
   deleting all that many repositories.

2) For some reason, Trac does not always display newly created
   repositories right away.  Not sure why.  Restarting Apache fixes
   this, but it would be nice to find a less drastic solution.