I wonder why this should produce this effect? I mean, why is it working with
99% of all paths, but not with some others?
BTW, it seems 1.6.12 does not know an options named force-username-case.
Thanks
-Markus
From: Jan Keirse [mailto:jan.kei...@tvh.com]
Sent: Freitag, 23. November 2012
Just a wild guess: does your username (in AD or as you entered it in the
svn client) have the same case as the authz file? Windows doesn't care but
the authz file does.
My apache configuration has this setting to accomodate for this:
AuthzForceUsernameCase lower
I _think_ svnserve can do the same
Hello Subversion Community,
do you know any relationship between LDAP and paths in svn?
I am running svnserve 1.6.12 on Debian 6.0.6 "squeeze" and it works
really well, but now I wanted to switch from plain passwd file to
SASL-LDAP (ActiveDirectory) based authentication and trapped into a
r
> Daniel Shahaf wrote:
> > Oscarsen, Anders wrote on Wed, Nov 21, 2012 at 15:17:39 +:
> > Hi,
> >
> > I've noticed something I don't understand when handling members of
> > multiple groups with different permissions.
> >
> > With this authz file:
> >
> > #--
Philip Martin wrote on Fri, Nov 23, 2012 at 11:12:01 +:
> net_robber writes:
>
> > XML: char-data (274) returns 0
> > XML: start-element (274, {svn:, close-file}) => 279
> > XML: end-element (279, {svn:, close-file})
> > XML: char-data (274) returns 0
> > XML: XML_Parse returned 0
> > XML: Pa
net_robber writes:
> XML: char-data (274) returns 0
> XML: start-element (274, {svn:, close-file}) => 279
> XML: end-element (279, {svn:, close-file})
> XML: char-data (274) returns 0
> XML: XML_Parse returned 0
> XML: Parse error: XML parse error at line 384: not well-formed (invalid token)
Do
