Stephen Bloch wrote:
> I'm teaching myself svn this month, in order to teach it to my Unix
> students :-)
> The error message went away when I disabled path-based access control,
> but that seemed like a drastic solution.
> So I checked the obvious things: had I given myself access to the path
> in question (yes, I had). Just to make sure, I went through the entire
> authz file looking for my username. In every single place that it
> appeared, it was the first entry, and it had rw access. (Which is also
> a drastic solution...) Even so, I kept getting this error message when
> I checked out a project that I had just imported five minutes earlier.
> I did some Googling and found one counterintuitive answer: put
> anon-access = none in svnserve.conf
> This doesn't make any sense: if I'm not trying to log in anonymously,
> why should anon-access matter to me? And why should DECREASING the
> access available to anonymous users have the effect of INCREASING the
> access I have? But it works: I put anon-access = none into the
> svnserve.conf file, and now I can get at my own directories.
> Is this a bug, or a really weird feature whose benefit I don't understand?
What version of the client are you using?
What platform are you using it on?
What repository access method are you using?
Knowing each of the above, along with the exact series of commands you are using
can help us diagnose your problem.
Received on 2008-11-21 04:29:34 CET