On Wednesday, December 14, 2016 at 6:51:33 AM UTC-8, Dave Love wrote: > > I upgraded to 1.0 from a 0.12 installation, and thought things were > working OK. Then I did a repo commit and found that they weren't. The > commit hook now tries to sync the repo from the start, not the just for > the new patches. (This is using darcs as the VCS; the trac-darcs author > tested 1.0 a while ago, but I don't know if that included the hook. It > was also with an OS upgrade and a new version of Python, but I doubt > that's relevant.) > > Are there any suggestions for what to look at to debug it, e.g. relevant > areas changed between the releases? Thanks. >
I don't recall anything having changed in going from 0.12 to 1.0 that would result in the behavior you are seeing. Could you share the content of the hook script? You could start by confirming that the "changeset added" command is being correctly called, and that [trac] repository_sync_per_request is set to an empty value. https://trac.edgewall.org/wiki/1.0/TracRepositoryAdmin#QuickStart - Ryan -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
