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

Re: svn repository issue

From: Ryan Schmidt <subversion-2008c_at_ryandesign.com>
Date: Thu, 11 Dec 2008 17:34:17 -0600

On Dec 10, 2008, at 19:26, Yong Shiuh Rong wrote:

> I manage to convert CVS to SVN recently, but i think i created the
> repo wrongly
>
> i have a folder /svn/repos/abc where abc should be the repo folder,
> anything under abc is the module, but now all the modules /svn/
> repos/abc/xyz itself is the repo, not abc, i think i must have done
> something wrong while importing it to svn, is there anyway to fix it?

So you wanted a single repository /svn/repos/abc but you ended up
with several repositories inside a directory /svn/repos/abc.

Yes, you can change this now. You will need to dump each of your
existing repositories (e.g. for each repository, do something like
"svnadmin dump /svn/repos/abc/repo1 > /path/to/dump1"), then move the
existing repositories out of the way ("mv /svn/repos/abc /svn/repos/
abc-old"), create the new repository ("svnadmin create /svn/repos/
abc"), then load each of the dumpfiles into the new repository.

There are two ways you can load the dumpfiles into the new
repository. One is the way Subversion provides built-in: "svnadmin
load /svn/repos/abc < /path/to/dump1" and so on for each dumpfile.
The disadvantage of this method is that the revisions of the new
combined repository will not be in chronological order, which means
you can never reliably use the Subversion feature of finding a
revision based on a date (e.g. "svn log -r {2008-12-11}"). If that
feature is important to you, you should load using a script like
svndumptool instead.

http://svn.borg.ch/svndumptool/

You can use svndumptool's "merge" command to merge multiple dumpfiles
into a single dumpfile where the revisions of all dumpfiles are
combined in chronological order. Then you can load that merged
dumpfile into your new repository.

Regardless which method you use, any existing working copies will be
invalid and you will need to check out new ones. So if you can,
commit any remaining changes in your working copies before doing the
conversion. Also note that most of your revisions will be renumbered,
so any references to revision numbers in your commit messages or in
an issue tracking system will be incorrect.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=983116

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2008-12-12 00:35:17 CET

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