Skip to content


svn: Not authorized to open root of edit operation

If you are trying to check something out from an svnserve daemon, and keep seeing this error:
/build/buildd/subversion-1.3.1/subversion/libsvn_repos/reporter.c:822: (apr_err=220000)
svn: Not authorized to open root of edit operation

you can fix it easily by going into $SVN_REPOS_ROOT/my_project/conf/svnserve.conf and changing line 12 from # anon-access = read to anon-access = none. It wouldn’t hurt to uncomment line 13 either…

Posted in Software Development, Subversion.


2 Responses

Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.

  1. rcampbell says

    This dose not seem to work if you are using Apache with mysql auth. Are there any other suggestions?

    In $path_to_repos/repo/conf/svnserve.conf all the lines are commented out because I’m using apache to access the repo.

    The subversion.conf for apace to read
    httpd/conf.d/subversion.conf:

    DAV svn
    SVNParentPath /var/svn/repos
    SSLRequireSSL
    AuthType Basic
    AuthName “MySQL group authenticated zone”
    AuthMYSQLEnable on
    AuthMySQLUser authuser
    AuthMySQLPassword **********
    AuthMySQLDB auth
    AuthMySQLUserTable users
    AuthMySQLNameField user_name
    AuthMySQLPasswordField user_passwd
    AuthMySQLGroupTable groups
    AuthMySQLGroupField user_group

    require group svn

    All the files are visible to both Apache and svn

  2. jtanium says

    The svnserve.conf file is only used by the ‘svnserve’ binary that’s part of Subversion. If you’re using Apache then the svnserve.conf is completely ignored, so naturally, what I posted is not going to work.

    There’s an Apache directive (I think it’s part of the dav_svn module) called AuthzSVNAccessFile. I would think that’s what you want to look. It’s discussed in Chapter 6 of the SVN Book.

    The file referenced by the AuthzSVNAccessFile directive specifies access control to your repository (or repositories), in a manner similar to what svnserve.conf. I can’t really be more specific because so far I haven’t had the need to define access control for my repositories.



Some HTML is OK

or, reply to this post via trackback.