Samay wrote:
The fact that you have managed to
check out the repo first means that this is an intermitted failure?
no, this was an already checked out repo, however, creating a fresh
checkout fails too, every time.
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).
nothing on server logs, and as it works fine with firefox, and on SVN on
Win32 clients, and not SVN + Linux it seems like a Neon related
somewhere. Here is output of Neon Debug 130
You should check if you have a 'guest' account enabled on the server.
The error message from Subversion 'authorization failed' indicates that
the *authentication* worked, but the authenticated user isn't authorized
to access the repository. If you have user 'guest' (or something
similar) enabled, then authentication will always succeed with that
user, but I doubt you gave that user access to the repositories.
If you can fix the issue by disabling that user account, you should also
report this on the Subversion dev list. I've tried to urge them to
implement something to disable automatic authentication (which is
possible in neon0.26 now, thanks Joe btw :), but somehow I got the
feeling they don't see that as a big problem. It should at least be
possible to fall back to basic authentication in such cases.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
_______________________________________________
neon mailing list
[email protected]
http://mailman.webdav.org/mailman/listinfo/neon
