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

RE: How to make projects with externals usable after the repository has been relocated?

From: Watson, Chris <cwatson_at_ptc.com>
Date: 2007-01-12 16:27:29 CET

sed unfortunately doesn't deal with the long line lengths that an dump
file has + of course you need to deal with the dump file elements that
encode data length. We ended up putting a script together in python to
do this - see attached. It chugged through about 20 repositories for me
without any problems, but no support/warranty is supplied or offered.
Basic Process:
  Generate Dump File
  Run replace script for each different replacement
  Load Dump File into fresh repo


From: Robert Ioiart [mailto:rioiart@gmail.com]
Sent: 12 January 2007 14:27
To: users@subversion.tigris.org
Subject: How to make projects with externals usable after the repository
has been relocated?

I made some external definition for a directory in my repository
pointing to another project(a release) in the
same repository. Then I dumped the repository and moved it to another
machine. The checkout on the new
repostitory failed because the external definition still pointed to the
URL in the old repository,
which did not exist any more.
This means, that after moving a repository with external defintions,
projects with external definitions are unusable.

Is there a way to define external definitions "relatively" (within the
same repository of course)?
Is it possible to modify the external definitions in the svn-dump,
before loading it into a new location? I tried replacing the paths with
sed but I get the following error when loading the newly applied file:
 - the command I used to replace the path:
ects\/PC_Tools\/grADI\/SVN_REPOSITORY\//svn:\/\/tma0008s\//g' input >
where input is the repository dump
-the error I get when running the command: svnadmin load NEWPATH <
<<< Started new transaction, based on original revision 200
     * editing path : test ... done.

------- Committed revision 200 >>>

<<< Started new transaction, based on original revision 201
     * editing path : test ...svnadmin: Dumpstream data appears to be
the thing is that I tried this approach with a small test repository
with two projects, one project having an external set to the other
project ; dumping the repository, replacing the path, loading it in a
new repository. This small repo works, but with the 500 MB dump file it
does not.
Could someone please help me with this, I find it really frustrating?
Maybe someone has a pre or post commit hook to check the external path,
or something in this direction.
Bottom line:
How to make projects with externals usable after the repository has been
Thanks and regards,

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Received on Fri Jan 12 16:28:16 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.