RE: [TSVN] versioned files show as unversioned

Is it possible that the .zip file that they created ignores empty
directories or that your zip program does not create them? On most of my
working directories the tmp folder contains empty folders named prop-base,
props, text-base, and wcprops. See if your WC starts working if you
create these folders?

For what it's worth, I do lend my support for pushing for a public SVN
server somewhere. The zip file you have is at least twice as large as it
needs to be...

-----Original Message-----
From: Simon Large [mailto:simon@skirridsystems.co.uk]
Sent: Friday, July 22, 2005 1:04 PM
To: dev@tortoisesvn.tigris.org
Subject: Re: [TSVN] versioned files show as unversioned

T E Schmitz wrote:
> The OFBiz people provide weekly snapshots as a convenience. I can only
> presume that the developer checked the revision out with an svn client
> and zipped it up. What version he used, I don't know.

I really think you need to sort this out with the OFBiz people. Find out
what version of svn they are using. Maybe it is very old.

> In any case I would not be able to check a 100MB working copy out from
> their repository as we are on a slow dial-up connection. The UK has only

> 99% ADSL coverage and we are in the 1% - 28Kbits/s at most.

Sympathy. If you have read access to their repository, AND you can get a
useable working copy, then you should just be able to run SVN update on
that WC to get the changes. That should be a lot less bandwidth than
grabbing a complete WC, as you only download the changes.

>>> I think this is some kind of version incompatibility. Working copies
>>> (of other apps) which I checked out myself from our local server have
>>> a tmp folder in the .svn folders. OFBiz' .svn folders don't contain a
>>> tmp folder.
>>
>>
>> Try svn status -v
>
> returns
> "svn: Can't open '.svn/tmp/.classpath.tmp': The system cannot find the
> path specified."

If the command line client can't do it, nor can TSVN.

>> TortoiseSVN is a subversion client using the standard subversion
>> libraries in exactly the same way as the command line client does.
>> TSVN 1.2.1 uses the 1.2.1 subversion library.
>
> OK, but it ships with these libraries rather than relying on svn being
> installed. Therefore it should be neither here nor there which command
> line version I have installed.

Exactly right. It wasjust that if you want to make a direct comparison
between TSVN and the SVN client, they have to be using the same version.
But it looks like the problem is much deeper than that.

> Is there any version of Subversion that is /not/ supposed to have a tmp
> folder in the .svn folders? If there isn't, then this would indeed seem
> a broken check-out.

You would have to ask that on the subversion mailing list.

Simon

--
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org