[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: unknown update problem ...

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2007-12-27 09:27:14 CET

Darran Edmundson wrote:
>
> Hi All,
>
> I'm getting the following TortoiseSVN error when updating part of our tree.
>
> "...
> C:\cygwin\home\darran\trunk\projects\0722-TyrrellDiscovery\Design\SW-loadpoint\it03-supplyChannel.SLDPRT
>
> Added:
> C:\cygwin\home\darran\trunk\projects\0722-TyrrellDiscovery\Design\SW-loadpoint\saddle.dxf
>
> Error: In directory
> 'C:\cygwin\home\darran\trunk\projects\0722-TyrrellDiscovery\Design\SW-loadpoint'
>
> Error: Can't copy
> 'C:\cygwin\home\darran\trunk\projects\0722-TyrrellDiscovery\Design\SW-loadpoint\.svn\tmp\text-base\flange.DXF.svn-base'
> to
> 'C:\cygwin\home\darran\trunk\projects\0722-TyrrellDiscovery\Design\SW-loadpoint\.svn\tmp\flange.DXF.tmp.tmp':
> No error"

That "no error" is not good. Completely useless message and definitely
wrong: there *was* an error - otherwise the update would have succeeded.
But until now, I've never seens such an error message coming from
Subversion.

> If I then repeat the update from within the Design folder, I get
>
> "Error: Working copy
> 'C:\cygwin\home\darran\trunk\projects\0722-TyrrellDiscovery\Design\SW-loadpoint'
> locked
> Error: Please execute the "Cleanup" command."

That's expected: after a failed operation, the working copy is always
locked and requires a cleanup.

> Cleanup from within Design then gives a modal dialog saying:
>
> "Subversion reported an error while doing a cleanup!
> In directory
> 'C:\cygwin\home\darran\trunk\projects\0722-TyrrellDiscovery\Design\SW-loadpoint'
>
> Error processing command 'modify-wcprop' in
> 'C:\cygwin\home\darran\trunk\projects\0722-TyrrellDiscovery\Design\SW-loadpoint'
>
> C:\cygwin\home\darran\trunk\projects\0722-TyrrellDiscover...\it04-pipe.SLDPRT'
> is not under version control."
>
>
> At which point I delete the local directory
> C:\cygwin\home\darran\trunk\projects\0722-TyrrellDiscovery\Design
> completely and repeat the process ;-)
>
>
> This problem is occurring with updates on both of our local PCs but not
> on our debian machine. My partner is using TortoiseSVN version 1.3.2
> (build 5840) while I have:

I can only think of two reasons:
* you're using the cygwin svn client together with native svn clients
(TSVN, official command line client, ...) - *never*, *ever* use the
cygwin client with other clients, the cygwin client is unreliable and
can mess up your working copy completely.
* there are two files of folders in your repository which have the same
name but differ only in case. You can't check out such folders on
Windows, because the windows file system is case insensitive unlike the
Linux ones (btw: don't bash Windows for this, Apple does the same).

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu Dec 27 09:27:31 2007

This is an archived mail posted to the TortoiseSVN Users mailing list.