On Thursday, May 2, 2019 at 9:24:07 PM UTC-4, Robert Jacobson wrote: > > > 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 :) >
Glad to hear its fixed. The deploy command won't have a direct impact on the repository synchronization, it just extracts the static assets to a directory and creates the wsgi script. Maybe there is an unexpected side effect of deploy in your configuration. Could "restart web server" have been the important step? > 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. > Just to be sure, repositories should be defined in either trac.ini or the database. In theory you could use both, but the entries in each should be unique. If not, one of the entries will be ignored and the results could be confusing. You shouldn't, for example, define "reposA" in trac.ini and the database. But you could define "reposA" in the database and "reposB" in trac.ini. Most users choose to use just one of the repository providers. > 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. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/0a4d7c79-7733-4d6a-b011-cdddc958166d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
