Re: Can't commit because current already exists

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. 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.

I had initially thought that the problem was permissions: that
somehow the "current" file had gotten written by a different user
than usual, and now the usual user couldn't replace it. But the fact
that you see the problem when restoring a database dump, all as one
user, suggests that the network drive may be the problem.

-- 
To reply to the mailing list, please use your mailer's Reply To All  
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org