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

Re: How to relocate a subversion server

From: Ryan Schmidt <subversion-2007a_at_ryandesign.com>
Date: 2007-03-12 04:07:46 CET

On Mar 11, 2007, at 20:10, ying lcs wrote:

> Technically speaking, tar on 1 machine/untar on aonther should
> work, right?

If you're running the same version of Subversion, and the
repositories are FSFS-based, then yes. If the repositories are BDB-
based, then I believe you must also be sure that the version of BDB
is the same, and that the processor architecture endianness is the
same. If it isn't, or you're not sure, the safe way that would always
work is to svnadmin dump the old repo on the old machine, and
svnadmin load it into a new repo on the new machine.

> I don't understand why it creates a 'trunk' directory when I check
> out like this:
> svn co file:///srv/svn/repositories/test/trunk

Because that is what Subversion does. RTFM. From "svn help checkout":

usage: checkout URL[@REV]... [PATH]

   If specified, REV determines in which revision the URL is first
   looked up.

   If PATH is omitted, the basename of the URL will be used as
   the destination. If multiple URLs are given each will be checked
   out into a sub-directory of PATH, with the name of the sub-directory
   being the basename of the URL.

This means that since you did not specify a path in which to
checkout, it chose the last part of the URL, which was trunk. If you
wanted to check out your trunk to a directory called foo instead, you
should use:

svn co file:///srv/svn/repositories/test/trunk foo

-- 
To reply to the mailing list, please use your mailer's Reply To All  
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 12 04:08:33 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.