RE: Re: svn commit failure

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
Subversion 1.3.1,
apr 0.9.7
apr-iconv 0.9.7
apr-utils 0.9.7
berkeley db 4.3.28
neon 0.25.4
OpenSSL 0.9.8a 11 Oct 2005
zlib 1.2.3

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).

Otto

-----Original Message-----
From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
Sent: Tuesday, July 29, 2008 11:04 PM
To: users_at_tortoisesvn.tigris.org
Subject: Re: svn commit failure

Kruse Otto-MGI1929 wrote:
> Hi,
>
> My group has been running Tortoise SVN 1.3.3.6219 for version control
> of our code for many years (I know it is an old version). We have had
> a few minor issues that we worked out by looking at the documentation,
> but currently we have a puzzler we are stuck on.
>
> We created a branch/tag of our code at revision 2187 and called it
> IPTVHAL_010201. We switched our working view to that tag, made our
> changes, and then attempted to svn commit them to the archives. When
> we do this we get the message:
>
> Error Commit failed (details follow):
> Error Can't open file
> 'I:\subversion\sb\transactions\2372-1.txn\node.402.k*': The filename,
> directory name, or volume label syntax is incorrect.
>
> (where * in the string above is actually a square symbol)
>
> Note that we have made branches in this manner numerous times in the
> history of our program and have not experienced this problem before.
> Scanning the manuals, FAQs, and internet we have not found a solution.
> Please help, any clue would be appreciated.

Are you accessing your repository via file:/// ?
If yes, then you must first use the svnadmin tool (part of the official svn client) and dump your repository, then load it with the new version (i.e., you must upgrade your repository to the latest format that svn clients 1.5 use).

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
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org