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

Re: Complex VSS Migration - dealing with moved/branched version history

From: Alan Barrett <apb_at_cequrux.com>
Date: 2007-08-23 10:02:32 CEST

On Mon, 20 Aug 2007, Bicking, David (HHoldings, IT) wrote:
> Is it safe to say that nobody has an answer or suggestion concerning
> my questions below? Nobody has any insight into the plans or
> perceptions of the Subersion developers concerning migration of
> projects with checkered histories?

As far as I can tell, the issue is:

* you can use vss2svn to create an svn dumpfile that has the entire
  history of your project;
* you could use "svnadmin load" to import the dumpfile, but you don't
  want to import the entire project, you want only parts of it;
* you tried using svndumpfilter to extract the parts that you want, but
  it fails because some of the files or directories in the part that
  you want were originally copied from files in the part that you don't
  want, and svndumpfilter can't deal with this;
* you wish for a way of telling svndumpfilter to deal with this, or
  some other way of editing the dump file to deal with this.

I'd suggest trying the subversion dumpfile utilities from
<http://www.cs.berkeley.edu/~dsw/>. This will let you convert a
dumpfile into a directory hierarchy, edit the directory hierarchy, and
convert it back to a dumpfile. With some effort, you should be able to
find the revisions that are causing problems for svndumpfilter, manually
change the details of those revisions (say replacing the copied-from
pointer with a full-text copy of the data, and adding a note to the log
message). Then run the modified dumpfile through svndumpfilter again.

--apb (Alan Barrett)

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 23 10:00:32 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.