Thanks for the tip - I checked into it but found I am using backslashes in
my SVNParentPath directive:
<Location /CommonServices>
# Custom error
ErrorDocument 401 /401.html
# Where is the repository
DAV svn
SVNParentPath E:\products\CommonServices
SVNAutoversioning on
# How we authenticate
AuthType SSPI
AuthName "Subversion repositories"
SSPIAuth On
SSPIAuthoritative On
SSPIDomain ads.mckinsey.com
SSPIOfferBasic On
# Who can enter
Require valid-user
</Location>
Cheers,
Edwin
"Rowell, Geoff" <growell@ENVOYWW.COM>
08/02/2005 09:18 AM
To
<Edwin_Park@mckinsey.com>
cc
"svn-dev-list" <dev@subversion.tigris.org>
Subject
RE: Re: bugs in hook scripts on Windows
Ben Collins-Sussman [mailto:sussman@collab.net] wrote:
> On Jul 30, 2005, at 7:21 AM, Edwin_Park@mckinsey.com wrote:
> > * The REPOS parameter that is passed in to the batch script uses a
> > Unix-style forward slash '/' delimiter between the repository base
> > dir and the repository instead of the DOS-style backslash '\'. For
> > example, I have a repository named 'Nexus' under the 'E:\products
> > \CommonServices' directory. The REPOS parameter passed into my
> > batch script is: E:\products\CommonServices/Nexus. This has forced
> > me to resort to hardcoding the repository location in my hook
> > scripts because I cannot use the mangled path that is passed in.
>
> You said this is svn 1.2.0 on win2k. Which server are you using,
> apache or svnserve?
>
> Developers: is this indeed a bug?
I noticed this in 1.1.x and determined that it was caused, in my setup,
by the way that I specified the SVNParentPath directive in httpd.conf.
If I used forward or back slashes, that's what was passed to the hook
script.
I imagine that the way the "root" option of svnserve is specified has
a similar result.
Since I only use the hook script ".bat" file to call a Perl script,
any mixed slashes are easily dealt with. I consider ".bat" files to
be fasteners - not working parts.
-Geoff
+=========================================================+
This message may contain confidential and/or privileged
information. If you are not the addressee or authorized to
receive this for the addressee, you must not use, copy,
disclose or take any action based on this message or any
information herein. If you have received this message in
error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation.
+=========================================================+
Received on Tue Aug 2 23:00:24 2005