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

RE: Upgrading to 1.3.2: "svnadmin: File already exists"

From: Fernandes, Filipe (Bolton) <ffernandes_at_husky.ca>
Date: 2006-08-23 19:40:50 CEST

> Magnus Naeslund(k) wrote:
> Well I'm not sure, but I like to verify that dump/restore works when I
> upgrade to another svn version.
> Maybe you see that as silly, but I'm glad I tried it, as I found an actual
> problem (whatever reason for it).
> Ben Collins-Sussman wrote:
> > (Do you use 'svnadmin dump' as a backup? That's awfully slow. You
> > might just want to copy the repository.)
> Yes I use that format because I thought it was the most flexible format.
> This might not be optimal as our repository grows, but I'll examine that
> later.

I recommended and have been using subversion @ work for 18 months now and
I'm quite pleased with it. You guys have done a great job with it. We
moved from Visual SourceSafe that occasionally went corrupt and found that
to be unacceptable.

I watch this thread mostly for upcoming features and to monitor the
direction of the project. I'm by no means a developer that could contribute
to this project, but when coming across this thread it's a little unnerving
the lack of attention this issue is receiving especially since it concerns a
dump that should be completely portable across different versions

I too backup using a dump of the repository. So upon hearing of the
potential problem with upgrading a repository using a dump/load cycle, I've
attempted to do the same here and to my relief everything worked out great.
But I wish there would be some kind of consensus as to what the problem
might be instead of suggestion different backup alternatives like
hot-copying the repository or the like.

If it's merely an upgrade issue with loading the dump file from one version
of subversion to the next, I can deal with that; but if there's a bug in how
data is written to the dump file... I find that to be much more serious and
am willing to change backup strategies...


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 23 19:41:17 2006

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.