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

Re: ... is already a working copy for a different url

From: Bo Berglund <bo.berglund_at_gmail.com>
Date: Fri, 02 Feb 2018 19:09:17 +0100

On Fri, 2 Feb 2018 16:03:43 +0100, "Martin Bo Andersen"
<mba_at_logossmartcard.com> wrote:

>I couldn’t find FAQs addressing my problem, even though it’s probably simple, and the archives tried to help people that wanted something more than the basics.
>But I’m not trying to do anything “clever”.
>It’s just a checkout.
>(I’m using Tortoise, but I don’t think Tortoise is the cause of this problem ... unless it’s doing something I’m unaware of.)
>
>I have a directory structure with a folder and three subfolders
>Xsvn
>-- X1
>-- X2
>-- X3
>
>I can checkout X1, X2, and X3.
>When I try to checkout files from Xsvn to Xpc, I get “Xpc is already a working copy for a different url”
>
>If this is really true, then
>1) it is not on purpose - I don’t want it to be a working copy for a different url
>2) I don’t know which “different URL”
>3) I don’t know how to solve it.
>
>It’s possible that it WAS a working copy for a different URL, because I didn’t know how SVN wanted things, but I have re-arranged my folders, so there should be no such problem any more.
>How do I know which URL is the problem?
>How can I make SVN forget the wrong URL, so that I can use the folder for the right URL?
>
 
Why not go to a completely new and empty folder and check out your
project there?

But if you must use the existing folder:
If you delete the .svn directory in the target dir you are trying to
check out into then it stops being a working copy altogether...
Notice that .svn is a hidden folder so if you are on Windows you won't
see it unless you modify the Windows Explorer view properties to show
hidden files and folders.

-- 
Bo Berglund
Developer in Sweden
Received on 2018-02-02 19:10:10 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.