On Fri, Apr 21, 2006 at 09:43:09PM +1000, Samay wrote: > If you need more details, feel free to ask. Any suggested work arounds?
... > 5. [EMAIL PROTECTED] ~/repos $ svn up > svn: PROPFIND request failed on '/repos' > svn: PROPFIND of '/repos': authorization failed (https://svn.my.realm) ... > [EMAIL PROTECTED] sandbox]$ svn ci > svn: Commit failed (details follow): > svn: MKACTIVITY of > '/svn/sandbox/!svn/act/16c1adf6-6b0d-0410-9322-c1268cc03508': authorization > failed (http://pledge.my.realm) Note that these are two different failure cases: neon will refuse to use Negotiate over non-SSL connections, so that could explain the latter failure, but not the first case. The fact that you have managed to check out the repo first means that this is an intermitted failure? In the case using the https:// URL, I couldn't say. You should firstly check the server's error_log to see what it has logged in that case; if nothing is being logged by mod_auth_kerb, try increasing the LogLevel; if that doesn't help, turn on neon debugging and send in that output (enable via ~/.subversion/servers). Regards, joe _______________________________________________ neon mailing list [email protected] http://mailman.webdav.org/mailman/listinfo/neon
