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

Bug? Rename & Commit fails

From: Benjamin Rana <brana_at_b-rana.de>
Date: 2007-06-26 10:02:29 CEST

Hi,

I'm always getting the same error while trying to rename a directory.
I did following steps:

1. I renamed a few Files and a directory with the "Tortoisesvn-Rename-Command" and committed the changes without any errors.
2. Now i changed to the parent directory and renamed the folder which contains the files of step 1.
3. After that told Tortoise to make a commit of the current folder.
Tortoise reports following Changes: The directory with the new Name is added, all Files within the old directory and the old directory are deleted.
4. After starting the commit-process, it fails with following Error: "Commit failed (details follow): Item '<old dir name>' is out of date. You have to update your working copy first.

My working copy is up to date. I also checked out the directory at a new Place and tried the same procedure. It always fails.
After the (failed) commit, one thing is quite curious:
If i take a look at my working copy, i can see the old directory with a X-icon (delete) and the new directory with a !-icon (modifications). When i tell Tortoise to show me the modifications within the new directory, it shows me a File and a directory which are deleted. The curious thing is, that booth have been already renamed and committed in Step 1. (It's showing me the old names)

TortoiseSVN 1.4.4, Build 9706 - 32 Bit , 2007/06/09 09:44:02
Subversion 1.4.4,
apr 0.9.12
apr-iconv 0.9.7
apr-utils 0.9.12
berkeley db 4.4.20
neon 0.26.3
OpenSSL 0.9.8d 28 Sep 2006
zlib 1.2.3

Benjamin

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Jun 26 10:02:09 2007

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.