You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Marc Strapetz <ma...@syntevo.com> on 2007/10/08 16:30:58 UTC
svn log -g completely broken?
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?
--
Best regards,
Marc Strapetz
_____________
syntevo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn log -g completely broken?
Posted by Daniel Rall <dl...@collab.net>.
On Tue, 09 Oct 2007, Marc Strapetz wrote:
> > Could you copy ${REPOSITORY}/db/mergeinfo.db to ${REPOSITORY}/db/indexes.sqlite?
>
> Thanks, that fixed the problem.
Great!
> > 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.
Thanks -- that's what I'd expect. The indexes.sqlite file was created
(empty) after your upgrade. The old mergeinfo.db contained all your
merge history, but was no longer getting examined at runtime. You can
discard mergeinfo.db now that you've copied it over indexes.sqlite.
Re: svn log -g completely broken?
Posted by Marc Strapetz <ma...@syntevo.com>.
> 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 <ma...@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
Re: svn log -g completely broken?
Posted by "Daniel L. Rall" <dl...@collab.net>.
On Mon, 08 Oct 2007, Arfrever Frehtes Taifersar Arahesis wrote:
> 2007-10-08 18:30 Marc Strapetz <ma...@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
Re: svn log -g completely broken?
Posted by Arfrever Frehtes Taifersar Arahesis <ar...@gmail.com>.
2007-10-08 18:30 Marc Strapetz <ma...@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.