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

Commit failed when wc contains files not under version control

From: Jennifer Kesterson <Jennifer.A.Kesterson_at_jpl.nasa.gov>
Date: 2006-11-30 20:08:39 CET


Yesterday, one of our users tried to rename (svn move) a directory in
her working copy. This directory contains several subdirectories.

When she ran 'svn status' at the start, it reported three files not
yet under version control (an ? was in the first column of the status
output). She proceeded with 'svn move <old_dir_name>
<new_dir_name>'. The output shows that the new directory name is
scheduled for addition, and that the old name and its contents are
scheduled for deletion. Strangely, it did not report that the
contents are also scheduled for addition in the new directory.

Anyway, when she tried to commit, it failed:

        svn: Item '<path_to_directory' is out of date

On a hunch, I suggested that she first add the unrecognized files not
yet under version control to the repository, then try 'svn move'
again. When she did that, the commit was successful.

So, my question is: Before a user renames a directory in the wc and
commits, must all contents of the directory *always* be under version
control? Are there any other requirements necessary for this commit to work?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 30 20:09:58 2006

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