I had a similar problem which I posted on the Tortoise SVN mailing list.
My problem seemed to be with deleting large numbers of files from a
repository using Tortoise SVN. One of the developers I work with was trying
to delete
a folder which contain 3000+ files. The deletion seemed to work, the
deletion action was committed so all the files we're seemingly removed. Yet
when the repository is viewed through IE or svnadmin the files are still
there. The revision number has been incremented but the files remain.
Also, when another commit was attempted from this same developers machine
the files that should have been deleted we're visible again in the list of
files to commit. When I deleted this folder using SVN command line the
deletion worked fine. I solved my problem by using the command line that's
why I figured it was a Tortoise SVN issue.
Hope that helps in some way.
Server is on Windows XP version 0.35.1 with Apache 2.0.48
All developers are using Tortoise SVN 0.24 build 554 UNICODE
-----Original Message-----
From: Tom Brunet [mailto:tomab@cs.wisc.edu]
Sent: April 15, 2004 2:13 PM
To: users@subversion.tigris.org
Subject: Commits that aren't?
I'm running WinXP and connecting through SSH to a repository on a Redhat
Linux box. I can check out files from the repository just fine. I
commit and it goes through the messages saying I added files, transmits
file data, and I get the message "Committed revision 3.".
The problem is that after this, the actual repository is only at
revision 2, and that commit never occurred at the server, even though my
client told me that it did. Now, my working copy thinks it's at
revision 3, so I can't perform any more commands since the server
apparently doesn't know about revision 3. The only way to recover my
local copy is to checkout a fresh copy (which is at revision 2 without
my changes). Commits done by manually uploading the files to the Linux
box and doing commits on the server work fine.
Is there any reason why my client would tell me that it committed a
revision when in fact it didn't? Why does the client update its state
to a revision that is non-existent? Any suggestions for how to get
these commits to actually happen?
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 15 23:12:32 2004