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

Stripping svn:mergeinfo for 1.5 upgrade

From: Rupert Wood <Rupert.Wood_at_softwire.com>
Date: Mon, 2 Jun 2008 12:01:21 +0100

I'm preparing to migrate our svn repositories from 1.2.1 to 1.5. I have been using pre-release 1.5 clients myself for some time now and there are svn:mergeinfo properties in the repositories. I remember you stripped these entirely from svn's own repository during the upgrade using a custom svnsync.

What's the danger with the existing information and what's the best approach to take? I can see three options:

    1. Run svnmerge-migrate-history.py. Rather than strip out all old
       data this appears to strip out the initial copies only and
       leaves merged ranges of revisions intact - is that enough?

    2. Mimic your process, mechanically stripping out all mergeinfo
       and get everyone to make new checkouts of the affected paths.

    3. Locate all existing svn:mergeinfo data and commit property
       changes to remove it a few days before the migration - will
       this avoid everyone needing to refresh their WCs?

Is there a better idea I've missed? If I want to try and put the mergeinfo back afterwards using --record-only can I just use the numbers from the properties I removed or will these be wrong? For the most part I only copied / merged at the top of each project; there are very few paths with more than one svn:mergeinfo in their ancestry.

Thanks, and apologies if I've missed an old thread or FAQ. As an aside, I tried svn proplist -R on the repository roots via ra_local to find the existing svn:mergeinfo properties and it ran out of memory at 3.5GB. Is that a stupid thing to do / expected? I can reproduce this with 1.5.0-rc8 against the unconverted repositories. Running proplist against the second level directories individually worked fine. The repositories are 3-4 GB fsfs with 12,000 and 25,000 revisions respectively.

Received on 2008-06-02 15:58:43 CEST

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.