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

Re: What does this error mean?

From: Wayne J <wayne_at_zk.com>
Date: 2007-07-16 19:12:27 CEST

----- Original Message -----
From: "Ryan Schmidt" <subversion-2007b@ryandesign.com>
To: "Rory Clark" <roryslists@clarkzoo.org>
Cc: <users@subversion.tigris.org>
Sent: Saturday, July 14, 2007 7:57 PM
Subject: Re: What does this error mean?

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

Yes, this is probably what happens. I believe that this is a semi-serious
subversion bug. It seems that at least in some cases subversion (the client)
decides that it a file is should not be committed because of a problem
generates a commit error but commits the file anyway.

I am not sure I ever really understood why the commit I did failed but the
file that case causing the failure was actually committed causing my working
copy to be out of sync (it believed that file still needed to be committed.)
I think I recovered by creating a new working copy and merging the remaining
changes to that working copy.

I believe that this may be the same problem that was recently reported in
the extensive discussion on the handling of EOL style. At least one user
reported that when inconsistent EOL styles are encountered svn errors out on
the file (stops the the commit operation) but actually commits the bad file
before stopping. If I remember this particular user solved his problem by
committing over and over until all the files with bad EOLs were erroneously

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:12:06 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.