Thanks for responding. I fixed my problem, though I do not understand how what I did fixed it.
Apparently whoever migrated the Trac instance did not ever complete a "deploy" command, or they did it incorrectly. They did everything else (upgrade, wiki upgrade, repository sync), but not a deploy. After I ran deploy, all the missing changesets appeared in the repo browser in Trac. If you have an idea why that might be, I'd appreciate the feedback. Otherwise I'm just happy that it's working. FWIW, this is Trac 1.2.3 (I think, that's from memory). Since you took the time to attempt to answer my questions, I'll also answer yours :) Make sure you don't have conflicting repository definitions in the database > and the [repositories] section of trac.ini. The trac.ini definition matched the database -- at least, after I removed the incorrect one. Is that the output listing the bad repository, or the output after you > removed the bad repository definition? Sorry, that was the output after I removed the bad definition. Is it just that one changeset that's missing, or do you get the same > message with any random choice of changeset revisions? All changesets since the upgrade were reported as missing. Users continued to use svn-native tools to commit changes to the repo; those did not appear in the browser -- though they did in the database. All the "old" changesets were correctly reported in the browser. Thanks again for your time. -- 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.
