On Wed, Aug 5, 2009 at 10:40 AM, Ryan
> On Aug 4, 2009, at 20:58, Dan Stromberg wrote:
>> We have a quite large subversion repo. Actually, 6, but I'm mostly
>> interested in one I cloned to another using svnadmin dump | svnadmin
>> Things seemed to be going really smoothly, and then I tried to use an
>> old program I wrote that spiders around in our subversion directories,
>> svn:externals and comments looking to ferret out what changed from one
>> tag to another, using light set theory (OK, bags really).
>> But while the program works well on our old subversion server, on the
>> new subversion server it runs along for a while and then errors on a
>> missing peg revision. I checked the logs for when the directory was
>> deleted, and found that it was deleted one revision after my program's
>> trying to get it. And I svn list'd it at the desired peg revision,
>> and found that it wasn't there - nor was it there a few revisions
>> before that according to svn list. But svn log thinks it existed if I
>> check its parent directory.
>> Does svnadmin dump | svnadmin load mess with your peg revisions?
> svnadmin dump | svnadmin load should not renumber your revisions, unless you
> used svndumpfilter in between to exclude some items, depending on your
> svndumpfilter settings.
>> I'm using subversion 1.4.4.
> Try the current version, 1.6.3, and try svnadmin verify to make sure it
> thinks the repository is ok.
Sadly, we already have a bunch of commits against the new server on 1.4.4.
Is there a good way of getting just the recent commits from the new
server on 1.4.4, svnadmin dump | svnadmin load, and then putting back
in the recent commits that were on the new server?
BTW, some of the commits will be on both the old and new servers.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-05 21:48:04 CEST