On 7/14/07, Ryan Schmidt <subversion-2007b@ryandesign.com> wrote:
> On Jul 14, 2007, at 20:45, Rory Clark wrote:
>
> > And more importantly, how do I fix it?
> >
> > Error: Failed to add file 'D:\svnroot\Development\Some\File.cs':
> > object of the same name is already scheduled for addition
> > I'm getting this all over the place after a commit failed talking
> > to the server.
>
> It sounds like your commit succeeded, but your working copy doesn't
> think it did. Try checking out a new working copy. Verify that your
> changes did indeed make it into the repository. Make sure you don't
> have any other uncommitted or unversioned work in your old working
> copy. Then delete the old working copy and use the new one.
This is the kind of error my office gets after we have a commit that
succeeds, but fails on the "Bogus date" error. We have found that
keeping any locks on commit prevents the error, for whatever reason.
If we hit this error, we have got in the habit (yes it happens that
frequently) of reverting the folder with the problem right away, and
then going in and moving any added files off to a safe temp folder.
The next update gets the .svn Working Copy back in sync with the
Repository, which already has the newest files because the commit DID
succeed. If we don't do that right away, we have to go through the
more arduous process described by Ryan.
A couple of questions: what server and client versions/OS are you
using? We're on svn 1.4.3 on the SUSE Linux ES 10 server, and 1.4.x on
most of the Win32 clients. Do you ever see the same "Error: Bogus
date" message after a commit?
Thanks,
Jred
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 16 19:56:34 2007