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

SVN add Error - Not a working copy

From: jack nimble <jackbenimble999_at_gmail.com>
Date: Wed, 7 Mar 2012 06:56:58 -0500

'm trying to create a new entry in subversion for development. This is
based on a project which already exist in subversion. I don't want to have
it based on that version, because that's for reference only and can't be
changed.

I tried to export it using subclipse in sts/eclipse. However, when I import
the top level project into sts/eclipse, the project structure isn't
preserved.

The sts/eclipse project structure *is* preserved when I do a checkout. So I
checked out the project to a different directory path. Then, using cywin's
command line, I recursively removed all the .svn entries from the project
with a "find.-name".svn"-execrm-rf{} \;"

However, when I attempt to add the new project into subversion, I get an
"SVN add Error - Not a working copy" for the top level directory.

I've been checking/googling, and it this error occurs when an .svn file is
missing for the directory. So, somehow subversion is still aware of this
project despite the removal of all the .svn directories. If I go a level
higher, I'm in the "workspace" for sts, and (I don't believe) there are
.svn entries at that level.

Why does subversion think this is still a subversion project after I've
removed all the tags? How can I get this checked-out directory added as a
new entry into subversion?
Received on 2012-03-07 13:01:22 CET

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.