Yah I'm doing an experiment now to see if I can install an older version of tortoiseSVN and have it not mess up
the subversion working copy for cygwin.



On 11/4/06, Jim Grandy <[EMAIL PROTECTED]> wrote:
This problem is mentioned on the Wiki on the SubversionBuildInstructions page:

Windows: There are several options. You can get the .exe binaries directly from Tigris. For a nice GUI, we've had success with TortoiseSVN. Alternatively, use the Cygwin installer: the Subversion package is inside the "Devel" group. Note that the Cygwin build of svn (version 1.2.3) might have a problem with properly checking out a source tree. See this [http://svn.haxx.se/users/archive-2005-08/1408.shtml] posting for details.

If you elect to use the native Windows svn command line client, and also have the cygwin Subversion package, make sure to put it in your bash shell path in front of the cygwin bin directories, so you don't inadvertently use the cygwin 'svn' command by mistake. 

Henry, it'd be great if you would update this section of the wiki ( http://wiki.openlaszlo.org/SubversionBuildInstructions#Get_the_Subversion_client) to include your experiences and to clarify that the problem still exists in the 1.3.x version of the cygwin svn binary.

jim

On Nov 4, 2006, at 4:05 AM, Henry Minsky wrote:

Oh yeah, this was another reason I started using native windows svn client instead of cygwin's svn,
when I check out a branch, I sometimes get this error:


A    trunk/test/rpc/soap/https/version/webapps/axis/WEB-INF/classes/samples/encoding/ElementService.class
svn: Can't move 'trunk/test/rpc/soap/https/version/webapps/axis/WEB-INF/classes/samples/.svn/tmp/entries' to 'trunk/test/rpc/soap/https
/version/webapps/axis/WEB-INF/classes/samples/.svn/entries': Permission denied

I don't know what the issue is, and I did the check out again and it seemed to proceed, but
it doesn't make me feel safe with the tree I have got now.


--
Henry Minsky
Software Architect
[EMAIL PROTECTED]





--
Henry Minsky
Software Architect
[EMAIL PROTECTED]

Reply via email to