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

RE: Re: Issue with 1.5.0 version

From: Gennady Khokhorin <gok_at_aerometric-ak.com>
Date: Thu, 17 Jul 2008 10:00:47 -0800

Hello, Konstantin!
Thanks for the hint: I was not aware of Right-Button-Move and for sure
did move
folders by hand. Well, its time to read manual my guess.
Did fix my Repository and WC, it was small Inno installation file.

One question still remains: moving folder using SVN R-B-Move did not
update Repository
state. And in Explorer both source and destination folders are marked as
normal (green check icon).
I expected Repository should be in sync with WC tree.
Update command did restore moved folder in source and did nothing in
destination folder.
Do you know if such behavior by-design?

Happy programming!
Gennady

-----Original Message-----
From: Konstantin Kolinko [mailto:knst.kolinko_at_gmail.com]
Sent: Wednesday, July 16, 2008 2:19 PM
To: dev_at_tortoisesvn.tigris.org
Subject: Re: Issue with 1.5.0 version

Hi, Gennady!

Don't panic!
 as says the "HHGTTG"

This kind of behaviour sounds scary, and I do not know, what caused it,
but I think that similar effects can be caused by erroneously moving the
.svn folder along with its parent folder.

I have seen several times that one well-known IDE was causing such a
mess while doing moves and refactoring in it. Also, someone can mess it
up by moving and copying the folders in the Explorer or in some file
managers.

(You should use your right mouse button to drag the folders, and use SVN
Move command from the menu that appears when you release the button)

I suggest you the following steps:

1. Launch Repository Browser dialog from Tortoise SVN menu and check the
repository, whether the files are on their proper places.

2. In the Repository Browser dialog, select the root folder of your
repository and, using the context menu, open the Log (in Russian
translation: "journal") of it.

Check, what changes were committed to your repository.

3. In your working copy in Windows Explorer invoke the Properties on the
folders A, B and their parents.

In the Properties dialog there is Subversion page, where the repository
path of this folder can be seen.

Check, if the path displayed there is what you are expecting.

Also, on the root folder of your working copy, call Check for
modifications from Tortoise SVN menu, and see, what is shown there.

If the paths are not what you are expecting, or there are some files
that are "nested", or in some other weird state, you would better
checkout a new working copy.

4. I hope you did not loose any modifications, but look in the Recycle
Bin. The files may be there.

Ather your working copy becomes in consistent state, you may open the
Log for its root folder, and from that dialog it is possible to select a
revision and revert the changes that were made in it.

I hope it helps you.

2008/7/16 Gennady Khokhorin <gok_at_aerometric-ak.com>:
> Hello, All!
> Did mention that 1.5.0 win2000sp4 messed up files in one project
branch.
> First ran SVNCommite branch, lost folder B in repository but file from

> it moved up one level to folder A.
> Next SVNUpdate branch and work copy files in A substituted with files
> from A in repository, ea I lost files in A.
> Another SVNUpdate deleted some folders in working tree and kicked out
> from SVN control (.svn folder is gone)! Pretty scary.
> Any help or thoughts, please.
> Gennady
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-07-17 20:02:42 CEST

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

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