On 8/14/06, developer@wexwarez.com <developer@wexwarez.com> wrote:
> Sorry for the bonehead questions.
>
> So i did a remote import into my mbsrepos repository:
> svn import repostest http://xx.xx.xx.xx/svn/mbsrepos/repostest -m "test
> initial import"
>
> This worked fine. But then i decided to add a file:
> $ svn add repostest/trunk/file3.java
> svn: 'repostest/trunk' is not a working copy
>
> So when you perform an import it doesn't actually create all the .svn
> files that connect your files with the repository. How do you get that
> connection?
>
> I tried just performing an update and got the same error:
> svn update https://xx.xx.xx.xx/mbsrepos/repostest
> svn: 'repostest' is not a working copy
Import only takes the directory you point it at and loads it into the
repository.
If you want to keep that directory around *and* make it a WC, I think
you're looking for an in-place import.
http://subversion.tigris.org/faq.html#in-place-import
Since you've already done the import, you can either delete or move
the imported copy to another location, then check out from the
repository to the place where you need it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 14 19:19:15 2006