RE: Subversion checkin problem

Hi Xenon,

I am no expert in this issue, but could you confirm that

A) this problem is consistent for all files in your project or just some
selected files. If it is an arbitrary set of files then would it be
possible to identify some commonality. Even though you are indicating a
slow post-commit hook as an issue, could you confirm that this is the
case with a different set of files.

B) could you reproduce your problem using the svn command line tool from
the client, then from the server itself, using TortoiseSVN and AnkhSVN.
This will narrow the issue to svn issue from the client or server or
both, TortoiseSVN or AnkhSVN.

C) Could you please provide the version of your SVN Server, svn client,
TortoiseSVN and AnkhSVN

Thanks
Lakshman
-----Original Message-----
From: Chris 'Xenon' Hanson [mailto:xenon@3dnature.com]
Sent: Thursday, 4 October 2007 5:31 AM
To: users@subversion.tigris.org
Subject: Subversion checkin problem

   I posted this originally to the TortoiseSVN list:
http://thread.gmane.org/gmane.comp.version-control.subversion.tortoisesv
n.user/8278/focus=8279

   because I was using TortoiseSVN. However, the consensus over there
seems to indicate I have a Subversion problem (server or libraries)
rather than something specific to Tortoise. I also have AnkhSVN (plugin
for VC++) installed and have used it at times as well.

   I'll refer to my original posting to avoid duplicating the same info.

   Summary: 3 SVN users and a big (very new) SVN repository. If a user
checks in a change to a file, then does some more work and checks in the
same file again, there is a good chance the second check-in will fail
with the message:

"svn: The version resource does not correspond to the resource within
the transaction.
Either the requested version resource is out of date (needs to be
updated), or the requested version resource is newer than the
transaction root (restart the commit)."

   No amount of updating the file, updating the whole working directory
or 'cleanup' will resolve the problem. If I copy the changed file to
elsewhere, then update to get a fresh clean copy (which succeeds), then
over-write it with the changed file, commit STILL fails.

   At one point, I tried deleting the .svn/all-wcprops file and
updating. This seemed to solve the problem, but I was severely chastised
for doing this.

   Checking out a fresh working directory from the repository is 130Mb,
which takes a while over our LAN and a LONG while over the Internet to a
remote developer's office.

   I have a post-commit hook installed invoking the commit-email.py
script:
/usr/share/subversion/hook-scripts/commit-email.pl "$REPOS" "$REV"
--diff n -h 3dnature.com -s "svn commit:" devs@3dnature.com

   Questions:

   Any idea how this situation keeps arising? At the moment both I and
another developer are stuck in this state and unable to commit changes
to some files. It was suggested that a slow post-commit hook could be
the cause, is commit-email known to be susceptible to this?

   Any ideas how to get out of this state? Cleanup didn't help. I can
checkout a new working directory, but that's not a real viable solution
given the size of the repo, and the speed of the link between here and
our offsite developers. :(

   I'm really happy with Subversion, now if I could just get it to work
without a hiccup, I could go back to coding. ;)

   I'm ok to post parts of the repository metadata, but the entire .svn
directory is like 24Mb so that might be impractical.

   Thanks in advance for any advice.

-- 
      Chris 'Xenon' Hanson | Xenon @ 3D Nature |
http://www.3DNature.com/
  "I set the wheels in motion, turn up all the machines, activate the
programs,
   and run behind the scenes. I set the clouds in motion, turn up light
and sound,
   activate the window, and watch the world go 'round." -Prime Mover,
Rush.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
================================================================================================
EMAIL DISCLAIMER
This email and any attachments are confidential. They may also be subject to copyright.
If you are not an intended recipient of this email please immediately contact us by replying
to this email and then delete this email. 
You must not read, use, copy, retain, forward or disclose this email or any attachment.
We do not accept any liability arising from or in connection with unauthorised use or disclosure 
of the information contained in this email or any attachment.
We make reasonable efforts to protect against computer viruses but we do not accept liability
for any liability, loss or damage caused by any computer virus contained in this email.
================================================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org