We have our repo, hosted by github, and that sends the info to our git trac plugin, which does a git fetch on the local repo, and then it does this for each commit.
trac-admin (repo_location) changeset added '(default)' 8f543b4c57b6ce518a2c74d5535319fcdc26ff70 followed by trac-admin (repo_location) repository resync '(default)' 8f543b4c57b6ce518a2c74d5535319fcdc26ff70 which spits out: (/usr/lib/python2.6/dist-packages) entry.load(require=True) 8f543b4c57b6ce518a2c74d5535319fcdc26ff70 resynced on (default). Doing this manually by hand shows no obvious errors. When you then check the timeline, nothing is updated. Doing a git show-ref --heads does show the commit is there. Doing a http://.../changeset/8f543b4c57b6ce518a2c74d5535319fcdc26ff70 shows : No changeset 8f543b4c57b6ce518a2c74d5535319fcdc26ff70 in the repository Doing a full resync does fix the issue, but that takes almost ~25 mins each time. Trac is 0.12.1 Trac's docs say: changeset added <repos> <rev> [rev] [...] Notify trac about changesets added to a repository and repository resync <repos> [rev] Re-synchronize trac with repositories When [rev] is specified, only that revision is synchronized. Otherwise, the complete revision history is synchronized. Note that this operation can take a long time to complete. -- And that IS what we are doing, so I am lost. Any ideas / pointers on what the issue is ? -- 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.
