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

Re: Subversion eating up all memory (again)

From: Simon Large <slarge_at_blazepoint.co.uk>
Date: 2004-11-18 11:45:31 CET

Lukas Ruf wrote:
> komsys-pc-ruf:kernel!69> svn up
> svn: Failed to add file 'kprobes.c': object of the same name
> already exists
> komsys-pc-ruf:kernel!70> svn commit -m "Re-adding after time-out"
> kprobes.c Adding kprobes.c
> svn: Commit failed (details follow):
> svn: File '/svn/PromethOS/linux/2.6/trunk/kernel/kprobes.c' already
> exists

Find out what is happening with kprobes.c.

If it already existed in the repo then your local copy has somehow
become unversioned.

If it is a new file that you have just written and want to add, then it
looks like someone else has beaten you to it and added it already. SVN
will not overwrite an unversioned file with a versioned one because it
might be destroying your data.

Try renaming your local kprobes.c, do the update, then diff the files to
find out who did what and when.

This sometimes happens to me when I create a new file and send it as a
patch. Someone else commits it, and then I can't update because I have
an unversioned local file, and there is now one in the repo (mine!) with
the same name.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 18 11:52:48 2004

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.