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

Re: Can't commit because current already exists

From: Larry Martell <larry.martell_at_gmail.com>
Date: 2007-03-13 15:12:24 CET

On 3/13/07, Ryan Schmidt <subversion-2007a@ryandesign.com> wrote:
> On Mar 12, 2007, at 19:03, Larry Martell wrote:
>
> > I dumped the repo, and that ran successfully - it dumped up to
> > revision 3480,
> > which was the highest revision before this commit problem surfaced.
> >
> > I then tried to load the dump into a freshly created repo. This ran
> > up to rev
> > 1102, then it failed with:
> >
> > <<< Started new transaction, based on original revision 1103
> > * editing path : Dynamic View.xml ... done.
> > svnadmin: Can't move
> > '/cygdrive/h/Engineering/EA/SubversionRepositoryRestored/db/
> > current.tmp'
> > to '/cygdrive/h/Engineering/EA/SubversionRepositoryRestored/db/
> > current':
> > File exists
> >
> > However when I look in the SubversionRepositoryRestored/db dir
> > there is not a
> > file called current.
> >
> > Anyone know what I can do to repair this repository??
>
> Try restoring to a local hard drive, not the networked drive.

Yup, that was it! I copied the dump to a local drive and when I loaded it to a
local repo it loaded just fine.

> If that works, then this would be a datapoint you can give to someone who has
> the power to change it, showing them that the networked drive is
> causing these problems.

This incident was enough to convince them to allow me to move the repo
to a server.

Thanks to all!!
-larry

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 13 15:12:56 2007

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