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

Re[4]: [TSVN] 1.2.2... sad story

From: Flex <flex_at_datecs.bg>
Date: 2005-09-07 17:06:11 CEST

Wednesday, September 7, 2005, 3:34:14 PM, you wrote:

> On 9/7/05, Flex <flex@datecs.bg> wrote:

>> the 4347 build solved the problem with moving .svn folders, but still the
>> problem with the externals is here - it tries to move them and after failing
>> creates a sub-duplicates. The same situation as described in my report with
>> hidden files turned off.

> The problem of sub-duplicates is a Subversion issue I complained about
> a long time ago. I even opened an issue in their tracker:
> http://subversion.tigris.org/issues/show_bug.cgi?id=2188

Oh. Nasty.

But this is serious... considering that a single move of an "external" folder sets its status "Deleted" and it is actually executed the next commit thus ruining the external folder and all other projects that depends on it can't be checked out anymore. This is especially true for a "shared" folders since all other tends to used them - after the move now I can't checkout any of my projects anymore.

I can't get the big picture here since I'm pure tsvn user but... here's what I think happens: Just a simple misunderstanding between what user wants to do and how tsvn executes it:
--dir1 (//path/to/project/trunk/dir1)
--dir2 (//path/to/project/trunk/dir2)
--externaldir (//external/repository/externaldir)

this external dir cames as "svn:externals externaldir //external/repository/externaldir" property set on the trunk folder.

So the user(me) selects all folders inside project/trunk and tsvn moves them to another folder. In the case of dir1 and dir2 it is ok, however "externaldir" gets "moved" to the new folder with svn mv, hence deleted from the original location, while in this case it should be just shell-moved, skipped or operation aborted, anything but without executing a svn mv command on it.
I know it's not tsvn flaw because it just does what the user told it to do - move.
It is not svn flaw either - it executes the operation correctly (or almost correctly).
It is a user falw - not understanding that this operation is unsafe until he breaks all other projects.

However... can tsvn "mark" such a directories and use a shell move or just fail or skip instead of svn mv on them?
Received on Wed Sep 7 16:07:17 2005

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