Home/ Questions/Q 4604990
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T00:22:16+00:00

I am having a svn repository structure in the below format: scm — products

  • 0

I am having a svn repository structure in the below format:

scm
 -- products
      -- productA
            --vechiles 
      -- productB

Here scm is the root of the repository and productA, productB is under products repository which is inturn uder scm repository. vechiles repository is under productA
My SVN Version is 

srikanth@localhost:~$ svn --version
svn, version 1.6.6 (r40053)
   compiled Mar 23 2011, 12:15:08

My Apache dav_svn.conf file configuration is:

<Location /scm>
        DAV svn
        SVNPath /home/srikanth/svnrepo
        AuthType Basic
        AuthName "My products Subversion Repository"
        AuthUserFile /home/srikanth/M/data/users.dat
        AuthzSVNAccessFile /home/srikanth/M/data/conf.dat
        Require valid-user
</Location>

My conf.dat file which is used for SVNAccess is as below, 

[scm:/products/productA]  
srikanth = rw

My Problem is when I try to copy vechiles repository inside productA only as I have access only to productA repo, I am having the below error,
My SVN Copy command goes like this,

srikanth@localhost:~$ svn copy http://localhost/scm/products/productA/vechiles http://localhost/scm/products/productA/pvechiles -m "Copied vechiles to pvechiles"

Output I am getting is:

svn: Server sent unexpected return value (403 Forbidden) in response to PROPFIND request for '/scm'

Request to let me know what’s the problem behind this and guide me to proceed further.. Thank you, Srikanth

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Yes, this is a long-standing issue with the SVN client: issue 3242. It’s logged as fixed in 1.6.13; it’s a client-side issue so you’ll need to update your client versions.

    If you need to support older clients then you can apply the patch with this message to your mod-svn-authz on your server. This will permit OPTIONS and PROPFIND requests at the repository root for any authenticated user. AFAIK there’s no security risk but the patch was never accepted.

    • 0