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

Re: Does "Repair move" work in TSVN 1.9.2?

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Tue, 6 Oct 2015 20:38:15 +0200

On 06.10.2015 13:44, Kurt Pruenner wrote:
> Upgrading packages using the nuget package manager in Visual Studio
> leaves me with missing folders for removed old versions of packages
> and unversioned folders for the upgraded versions; I then always used
> the "Check for modifications" dialog to select the corresponding
> missing old and unversioned new folder and do a "Repair move" on them
> so unchanged files are just copied from the earlier revision.

I recommend installing AnkhSVN or VisualSVN for VisualStudio - it will
track any moves/renames/deletes automatically so you won't get into such
a situation anymore.

> But since upgrading to TSVN 1.9 (and both in at least 1.9.1 and
> 1.9.2) every time I do this I get an error dialog stating the
> following:
>
> [Window Title] TortoiseSVN [Main Instruction] Subversion reported an
> error: [Content] Path 'C:\Lokale
> Dateien\eCS\VMS\packages\EntityFramework.6.1.3' already exists as
> unversioned node
>
> I've encountered this on at least 2 occasions now, and have yet to
> successfully "Repair move" anything - does this work for anyone
> else?

Yes, works fine for me.
How were the folders moved? Meaning: what's the old path and what's the
new path?

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3141193
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-10-06 20:38:20 CEST

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

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