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

Re: Cygwin's svn client cannot write to a windows https repository

From: Andrey Repin <anrdaemon_at_freemail.ru>
Date: Fri, 28 Aug 2009 03:56:48 +0400

Greetings, Andy Levy!

>>>> The repository seems running on a Windows machine.  It use https as
>>>> connection protocol.
>>>> When using Windows svn client
>>>> (http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91),
>>>> there is no problem,  it even not ask for a user name and password.  But
>>>> when I use the svn client (1.6.4) comes from cygwin, the read operations
>>>> (e.g. ls, co) get no problem, but and write operation such as 'mkdir'  will
>>>> always result in an error:
>>>> svn: Server sent unexpected return value (403 Forbidden) in response to
>>>> MKACTIVITY request for
>>>> '/svn/LowCost/!svn/act/aaf33518-92b5-11de-8af7-c3c035929cdc'
>>>> What I did
>>>> has nothing to do with local working copy, since i am doing the 'mkdir' on the remote URL, there is no local copy involved at all.
>>>> Can anyone give me some help?  Thanks.
>>> If you already have the Win32 command-line client, why are you using
>>> the hack that is Cygwin?
>> Cygwin is not a hack.
>> How else you could force Subversion to export LF-wrapped files on Windows with
>> eol-style=native?

> If you require LF-wrapped files, then set eol-style=LF. Why use native
> if that's not really what you want?

Do you suggest me to do that every time before checkout?
And my other collaborators should revert that setting when they want them with
wrappings suitable for their tools?
I'm using tools that suitable for me. If I can save my repository
administrator a headache, i will certainly do that. In such case it means that
I'm using Subversion built against cygwin-1.dll to export certain progects to
my working copy.

>>> Cygwin tricks the client into thinking it's on an OS it's not, which leads
>>> to confusion and some problems.
>> You're seriously wrong if you thinking that way.

> Yet those problems have been documented on this very mailing list.

> Try it this way: you can't share a WC created under Cygwin with the
> Win32 SVN clients. You face many of the same issues you face when
> sharing a WC between Win32 and *NIX.

*sigh* Please stay on topic. All this your twist has nothing to do with OP's
problem. Not even a thing.

 Andrey Repin (anrdaemon_at_freemail.ru) 28.08.2009, <3:51>
Sorry for my terrible english...
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-28 08:29:21 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.