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

Is it safe to delete mergeinfo.db?

From: Eric Hanchrow <offby1_at_blarg.net>
Date: 2007-09-19 20:49:29 CEST

(I apologize if I've this is the second time I've asked this -- I
could have sworn I already did, but can find no trace of it)

I am running a version of the svn trunk compiled Aug 10 2007,
13:57:42, and have noticed some odd behavior when trying out the new
automatic merge-tracking feature:

    svn log -g file://$HOME/svn-repos/trunk/doodles/plt-scheme > /tmp/yow
    ../live/subversion/libsvn_fs_fs/tree.c:2709: (apr_err=160013)
    svn: File not found: revision 4525, path '/trunk/doodles/plt-scheme/irc-v2/bot.ss'

I assume that a combination of my not knowing what I'm doing, and a
bug in my old version of Subversion, has somehow screwed up
mergeinfo.db, and I don't particularly care about its contents anyway.

I'd like to upgrade my version of subversion and keep using my repo.
But I worry that my mergeinfo.db is in some bad state that is the
fault of old code (either the Aug 10 version that I'm currently
running, or one that's even older, which created it), and that if I
upgrade to a newer trunk version of svn, and still have the same
trouble, no developer will want to investigate, since the problem is
indeed likely to have been caused by old code. That's why I want to
delete it.

So ... can I safely nuke mergeinfo.db? For what it's worth, I made a
hotcopy of my repo, deleted the mergeinfo.db from that hotcopy, and
ran "svn log -g" on it; it completed with no errors.

-- 
Documentation exists, but never seems to be complete.
        -- Dennis Ritchie, 1972
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 19 20:49:42 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.