[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Migrate from svn:// to http://

From: Rahul <rahul8024_at_yahoo.com>
Date: 2007-06-14 12:07:05 CEST

Thanks Everyone,
            Dump and load worked.
            moving and changing permissions doesnt...
Rahul <rahul8024@yahoo.com> wrote: Hi Ryan,
        I tried what you suggested but it dint work
and while running 'svnadmin youngest' or 'svnadmin dump' m getting the following error
svn: Berkeley DB error while opening 'revisions' table for filesystem intranet1/db:

but if i run the same command on http:// on any repos it is working fine.....

is there any solution to this or that repos is corrupted

Ryan Schmidt <subversion-2007b@ryandesign.com> wrote:
On Jun 14, 2007, at 03:04, B. Smith-Mannschott wrote:

> On 6/14/07, Rahul wrote:
>> I want to migrate an existing repository which is there on
>> svn://protocol to http:// with all its revision intact. dont want
>> to change
>> anything expect the portocol and the server. I have a setu for
>> http://
>> already which is running for other repositories which are created
>> from
>> scratch but this one needs to be migrated
>> Can some one help me or even let me know some relevant doc so that
>> i can
>> proceed with it
> Have a look in "Version Control with Subversion" [1] at the svnadmin
> commands dump [2] and load [3].
> If you are using svn:externals to refer *to* the repository you are
> migrating, you'll want to rewrite those as well. 'revisionist' [4], a
> small python library I wrote, can help there.
> [1] http://svnbook.red-bean.com/
> [2] http://svnbook.red-bean.com/nightly/en/
> svn.ref.svnadmin.c.dump.html
> [3] http://svnbook.red-bean.com/nightly/en/
> svn.ref.svnadmin.c.load.html
> [4]
> 3Aaction=search&term=revisionist&submit=search>

In fact, rewriting svn:externals with such a script is the only
reason I can think of why you might want to dump and re-load. If you
don't use any svn:externals that point to this repository, then all
you need to do is move the repository on disk to the place where
Apache is expecting them, and change the ownership of the files to
the user under which Apache runs. If you have any existing working
copies of that repository that you would like to re-point to the http
URL, just use "svn switch --relocate svn://old/url/to/repo http://new/


Food fight? Enjoy some healthy debate
in the Yahoo! Answers Food & Drink Q&A.

Expecting? Get great news right away with email Auto-Check.
Try the Yahoo! Mail Beta.
Received on Thu Jun 14 12:07:29 2007

This is an archived mail posted to the Subversion Users mailing list.