Reverting tree conflicts may leave an working copy inconsistent with the repository
From: Jan Normann Nielsen <spam_at_dubbekarl.dk>
Date: Thu, 06 Aug 2009 12:56:16 +0200
Hi
I've noticed a (to me) very strange behavior with Subversion 1.6.3 when
http://subversion.tigris.org/files/documents/15/46144/svn-win32-1.6.3.zip
running on Windows XP Professional SP-3 with all the latest updates.
Attached are two files:
svn-error.txt: Actually a .bat file with a working example. Comments are
The example shows a simple repository and a set of operations that make
Can anyone tell me if this is the expected behaviour or a bug?
Best wishes,
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
rem Dump SVN details
rem Create repos
rem Check out the repository
rem Add file.txt
rem Update back to r0
rem Merge r1 changes from /trunk to show them as changes
rem Update to most recent revision. This will give a tree conflict
rem Show the tree conflict
rem Revert the tree conflict and the merge info
rem Show that file.txt has now somehow become unversioned although it's in the repository at this revision
rem Delete the unversioned file
rem Show that there are no local modifications of the working copy and just to make sure, update it again to the most recent revision
rem We now have an up-to-date working copy without file.txt but without any local modifications
C:\Documents and Settings\Jan\Desktop>rem Dump SVN details
C:\Documents and Settings\Jan\Desktop>svn --version
Copyright (C) 2000-2009 CollabNet.
The following repository access (RA) modules are available:
* ra_neon : Module for accessing a repository via WebDAV protocol using Neon.
C:\Documents and Settings\Jan\Desktop>rem Create repos
C:\Documents and Settings\Jan\Desktop>mkdir C:\repos
C:\Documents and Settings\Jan\Desktop>svnadmin create C:\repos
C:\Documents and Settings\Jan\Desktop>rem Check out the repository
C:\Documents and Settings\Jan\Desktop>svn co file://localhost/C:/repos
C:\Documents and Settings\Jan\Desktop>rem Add file.txt
C:\Documents and Settings\Jan\Desktop>cd repos
C:\Documents and Settings\Jan\Desktop\repos>echo Test 1>file.txt
C:\Documents and Settings\Jan\Desktop\repos>svn add file.txt
C:\Documents and Settings\Jan\Desktop\repos>svn commit -m "Add file.txt"
C:\Documents and Settings\Jan\Desktop\repos>rem Update back to r0
C:\Documents and Settings\Jan\Desktop\repos>svn update -r 0
C:\Documents and Settings\Jan\Desktop\repos>rem Merge r1 changes from /trunk to show them as changes
C:\Documents and Settings\Jan\Desktop\repos>svn merge -c 1 .
C:\Documents and Settings\Jan\Desktop\repos>rem Update to most recent revision. This will give a tree conflict
C:\Documents and Settings\Jan\Desktop\repos>svn update
C:\Documents and Settings\Jan\Desktop\repos>rem Show the tree conflict
C:\Documents and Settings\Jan\Desktop\repos>svn status
C:\Documents and Settings\Jan\Desktop\repos>rem Revert the tree conflict and the merge info
C:\Documents and Settings\Jan\Desktop\repos>svn revert file.txt
C:\Documents and Settings\Jan\Desktop\repos>svn revert .
C:\Documents and Settings\Jan\Desktop\repos>rem Show that file.txt has now somehow become unversioned although it's in the repository at this revision
C:\Documents and Settings\Jan\Desktop\repos>svn status
C:\Documents and Settings\Jan\Desktop\repos>rem Delete the unversioned file
C:\Documents and Settings\Jan\Desktop\repos>del file.txt
C:\Documents and Settings\Jan\Desktop\repos>rem Show that there are no local modifications of the working copy and just to make sure, update it again to the most
C:\Documents and Settings\Jan\Desktop\repos>svn status
C:\Documents and Settings\Jan\Desktop\repos>svn update
C:\Documents and Settings\Jan\Desktop\repos>rem We now have an up-to-date working copy without file.txt but without any local modifications
C:\Documents and Settings\Jan\Desktop\repos>pause
|
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.