But you just said "One, it means you have not configured your Apache to
serve this directory as a repository. You need to move that svn directory
outside of the DocumentRoot and then set up Apache to serve the repository
like this:" ??
On Thu, Feb 19, 2009 at 10:12 PM, Ryan Schmidt <
> On Feb 19, 2009, at 06:31, Lasse A. Karlsen wrote:
> On Thu, Feb 19, 2009 at 5:49 AM, Ryan Schmidt wrote:
>> On Feb 18, 2009, at 18:15, Lasse A. Karlsen wrote:
>>> Hi everyone! I'm desperately trying to backup my google code-repo but
>>>> since I'm not too familiar with SVN, I can't get svnsync to work.
>>>> I thought that backup up your repo to another repo or dumpfile was an
>>>> easy task, but I'm I wrong?
>>>> What I'm trying to do:
>>>> norsof@shell:~$ svnsync init http://www.norsof.org/svn/ http://
>>>> svnsync: PROPFIND request failed on '/svn'
>>>> svnsync: PROPFIND of '/svn': 301 Moved Permanently (http://
>>>> What does that mean? And is it possible to fix it?
>>>> http://www.norsof.org/svn/ was created with svnadmin create, ofc.
>>> When I look at http://www.norsof.org/svn/ in a web browser, I just see
>>> the directories conf, dav, db, hooks and locks, and the files format and
>>> pre-revprop-change.cmd. There are two things wrong with this. One, it means
>>> you have not configured your Apache to serve this directory as a repository.
>>> You need to move that svn directory outside of the DocumentRoot and then set
>>> up Apache to serve the repository like this:
>>> <Location /svn/>
>>> DAV svn
>>> SVNPath /path/to/where/you/moved/svn
>>> Two, the file pre-revprop-change.cmd will have no effect directly inside
>>> the repository directory. It needs to be in the hooks directory if you want
>>> Subversion to use it. But it also appears to be empty so maybe it's a
>>> leftover file from when you were testing something.
>> Hey and thanks for great response! But what do I do when I don't have
>> permissions to change the httpd.conf file? Is there an easy way to dump this
>> to a file (and still preserve all the history..) ?
> You can svnsync the remote repository to a repository you create on your
> local computer, on which you presumably have permissions to do anything you
> want. Note that you don't even need to set up apache or svnserve; you can
> sync to a repository you just created with "svnadmin create". Then, once the
> sync is done, you can do whatever you want with your copy of the repository,
> including svnsync it somewhere else, svnadmin hotcopy it, svnadmin dump it,
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-20 16:48:25 CET