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

svn: Commit failed (details follow): 'file' is not under version control

From: Mark E. Hamilton <mhamilt_at_sandia.gov>
Date: Fri, 09 May 2008 10:23:09 -0600


I've got a situation with SVN that seems inconsistent. I'm using this
version of SVN:

sahp7635% svn --version
svn, version 1.5.0 (Release Candidate 4)
    compiled Apr 25 2008, 16:46:48

I have a sparse working directory that contains a file which has been
ignored, and some sub-directories, some of which were updated and some
of which were checked out (so my working directory is disjoint so I
can't just do 'svn commit -m Test'.) I can get the status using a wildcard:

% svn status *
M Nbtools/Jamroot
I SNTools.project
M Sierra/Sierra.xml
M aria/Apps_aria.C

and it ignores the ignored file. However, when I try to commit with the
same wildcard it fails:

% svn -m Test commit *
svn: Commit failed (details follow):
svn: '/var/scratch2/sierra_svn_votd/SNTools.project' is not under
version control

I would understand if it whined about a file that was not under version
control and not marked as ignored, but it seems to me that in this case
it should ignore this file even for a commit. Not being able to do this
means that we have to explicitly specify each sub-directory we want to
commit, which means that something could be missed. I don't know if
this behavior is intentional or a bug. Is there a reason why allowing
this commit would be an unwise thing for SVN to do?

Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-09 18:23:43 CEST

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.