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

Re: Is this a bug?

From: Marcus Comstedt <marcus_at_mc.pp.se>
Date: 2002-07-21 16:07:06 CEST

Ben Collins-Sussman <sussman@collab.net> writes:

> How do you make this happen? It seems to work fine for me in r2591:
> $ svn cp file:///home/sussman/projects/test/repo/A/D wc/A/C

> By the way... I hope you're not trying to do 'svn cp URL wc-path'
> where the URL and wc-path are from two different repositories. That's
> guaranteed to fail when you try to commit. :-)

I believe he's trying to do 'svn cp URL path' where path is not a
wc-path at all. Like this:

pelix:~% ls .svn foobar
.svn: No such file or directory
foobar: No such file or directory
pelix:~% svn cp http://svn.collab.net/repos/svn/trunk/subversion/svnadmin foobar
A foobar/main.c
A foobar/svnadmin.h
A foobar/svnadmin.dsp
A foobar/svnadmin.1
A foobar/shell.c
Checked out revision 2608.

svn_error: #21044 : <Path is not a working copy directory>
  svn_wc_entry: . is not a working copy directory

So in this case the error message is correct. '.' isn't a working
copy directory. Question is, if that's a problem, shouldn't the
command fail _before_ writing all the files to foobar? And if it
isn't a problem (foobar seems to become a proper wc dir), then there
shouldn't be an angry message about it.

  // Marcus

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jul 21 16:13:29 2002

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.