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.
Question:
Is there a way to define external definitions "relatively" (within the same
repository of course)?
OR
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:
*sed
's/file:\/\/\/\\tmav351x.tmav.ww011.siemens.net\/did94044\/IIP_CDS\/Projects\/PC_Tools\/grADI\/SVN_REPOSITORY\//svn:\/\/tma0008s\//g'
input > output*
where *input* is the repository dump
-the error I get when running the command: *svnadmin load NEWPATH < output*
...
<<< 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
malformed
==================
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
relocated?
Thanks and regards,
Robert.
Received on Fri Jan 12 15:27:30 2007