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

Re: Is it safe to delete mergeinfo.db?

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-09-19 21:28:48 CEST

On 9/19/07, Malcolm Rowe <malcolm-svn-dev@farside.org.uk> wrote:
> On Wed, Sep 19, 2007 at 02:53:54PM -0400, Mark Phippard wrote:
> > > 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.
> >
> > Yes you did already send. Dan Rall indicated you can just delete the
> > .db file and it will be created again the next time something needs to
> > write to it.
> >
>
> Will it be recreated _empty_, or will it be repopulated with the
> existing mergeinfo data? (I assume we need the latter behaviour
> somewhere anyway (though perhaps we're planning to make it explicit),
> since we'll nee some way of migrating pre-1.5-era-svnmerge.py
> properties?)

It seems like someone needs to show real problems and corruption in
the database before we ought to go that far. I do not think it has
anyway to populate itself from the repository contents. It just
creates empty as a by product of making it easy for existing
repositories to be used with 1.5.

I cannot see svnmerge.py script doing anything other than converting
the property format and letting the normal property handling routines
populate the database.

If someone needs to recreate the info, shouldn't they dump/load?

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 19 21:29:00 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.