# RE: Re: svn commit failure

From: Kruse Otto-MGI1929 <otto.kruse_at_motorola.com>
Date: Wed, 30 Jul 2008 13:34:08 -0400

Stefan,

Thank you, we will try this out and reply back on the users thread. If this does not work out then we will schedule an upgrade to the latest Tortoise and Subversion in the next couple of weeks.

Otto

-----Original Message-----
From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
Sent: Wednesday, July 30, 2008 9:50 AM
To: users_at_tortoisesvn.tigris.org
Subject: Re: svn commit failure

Kruse Otto-MGI1929 wrote:
> To answer your question the branch is referred to in the Tortoise
> Dialog as file:///I:/subversion/vip/branches/IPTVHAL_010201_1
>
> You didn't ask for it, but here is my full configuration (I should
> have supplied that on the first email)
>
> TortoiseSVN 1.3.3, Build 6219 - 32 Bit

Autsch!
You realize that this is a very ancient version?

> My understanding is that you are suggesting that I upgrade to the
> latest client. I know for certain that will not work with base
> Subversion 1.3.1 (we inadvertently have done that before). If
> upgrading everything to the latest will solve this problem so be it,
> we can start down that path, but I am not sure that is what is causing
> the current problem. We are currently able to svn commit to our Trunk
> code and branches that were created previously with no issue. We are
> just not able to svn commit to this new branch (have tried creating it
> in numerous ways, all exhibit the same issue).

You're using file:/// to access a repository on a network share. Please have a look at the big warning in our docs:
http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-repository.html#tsvn-repository-local-share

It seems your repository got corrupted. I hope you have a good backup.
Get the svn command line client for your version (1.3.x) from here:
http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=469&expandFolder=469&folderID=91
(note that even that folder is now called "archive").

Then run
$svnadmin verify path\to\repository it will report some errors in your repository. Then try running$ svnadmin recover path\to\repository

maybe recovering works, but I wouldn't bet on it.
Once you got your repository back to a working state, either with 'svnadmin recover' or from a backup, take the time to set up a proper server and quit using file:/// to access your repository. Setting up a server on Windows is done in 5 minutes if you're using the VisualSVN server:
http://www.visualsvn.com/server/
if your server is running Linux, it will take you about one or at most two hours to set up the server. Please take that time! It's really worth it.

Stefan

--
___
oo  // \\      "De Chelonian Mobile"
(_,\/ \_/ \     TortoiseSVN
\ \_/_\_/>    The coolest Interface to (Sub)Version Control
/_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org