[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn log -g completely broken?

From: Daniel L. Rall <dlr_at_collab.net>
Date: 2007-10-08 20:35:44 CEST

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.

- Dan

  • application/pgp-signature attachment: stored
Received on Mon Oct 8 20:36:26 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.