Scott Lamb wrote:
> I updated my client's neon to 0.23.5 and apr/apr-util/subversion to the
> latest (3598) and now I get this error message on checkin:
>
> subversion/libsvn_client/commit.c:628: (apr_err=175002, src_err=0)
> svn: RA layer request failed
> svn: Commit failed (details follow):
> subversion/libsvn_ra_dav/util.c:412: (apr_err=175002, src_err=0)
> svn: MKACTIVITY of
> /svn/repos/!svn/act/0de13410-56ae-0310-9a19-a8544f16a50c returned status
> code 401 (Authorization Required)
>
> The server does require authorization on checkin, but that's not new. I
> haven't changed the Apache config, upgraded the server, or anything.
Okay, gstein reminded me on IRC to check the server's error_log (duh).
It said:
auth_ldap authenticate: user authentication failed; URI
/svn/repos/!svn/act/dc304acb-55ae-0310-85bf-e3a3d4ca9180 [User is not
unique (search found two or more matches)][No such object]
That's what auth_ldap seems to say when you pass it a blank username. I
explicitly did "--username slamb" on the commandline. It error_logged
about a blank password and the client prompted for user/pass. I entered
them and it worked.
Is it possible that my working copy's .svn/auth/{username,password}
would get messed up somehow? I'm afraid I didn't think to cat their
contents first.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 1 16:52:22 2002