Re: svn log -g completely broken?

> Could you copy ${REPOSITORY}/db/mergeinfo.db to ${REPOSITORY}/db/indexes.sqlite?

Thanks, that fixed the problem.

> Marc, please let us know how this works out for ya. Also, please confirm
> whether you see both a mergeinfo.db and an indexes.sqlite file within your
> REPOS/db/ directory.

Yes, both files had been there.

--
Best regards,
Marc Strapetz
_____________
syntevo.com
Daniel L. Rall wrote:
> On Mon, 08 Oct 2007, Arfrever Frehtes Taifersar Arahesis wrote:
> 
>> 2007-10-08 18:30 Marc Strapetz <marc.strapetz@syntevo.com> napisał(a):
>>> With r27021 "svn log -g" does not output any merge information resp.
>>> merged revisions at all. I have tried logging an URL and logging my
>>> local WC. When going back to r26871, "svn log -g" works as expected
>>> again with the same repository. Am I missing something here?
>> Could you copy ${REPOSITORY}/db/mergeinfo.db to ${REPOSITORY}/db/indexes.sqlite?
>>
>> If it doesn't work, then try to find exact revision which created this problem.
> 
> That's a good hunch, Arfrever -- r26947, which renamed the SQLite database
> in which we're keeping our merge history index, falls within the range that
> Marc has just upgraded to.
> 
> Marc, please let us know how this works out for ya.  Also, please confirm
> whether you see both a mergeinfo.db and an indexes.sqlite file within your
> REPOS/db/ directory.
> 
> Thanks!
> - Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org