RE: Need advice: svnadmin dump and load between different versions of subversion?

Andrey, thanks for the reply. No, I don't believe I can compile svn 1.5 or 1.6 under my current Sarge server. I believe there were issues with Python upgrades. I'll look into it again, but I don't think I can use this solution. I'd rather just upgrade to Lenny instead, but management won't approve this yet.

I guess what I really need to know is whether I should even do the dump, filter and load with the newer svn and run it under the old svn. What sort of problems do you think I can run into? If there's a chance of data corruption then I will just tell management I won't be able to filter out the modules they want removed. I just want to know if it's crazy to try something like this.

Regards,

Timothy Kallinis
Xandros Corporation (www.xandros.com) | 613-842-3494 x441

----- Original Message -----
From: Andrey Repin <anrdaemon_at_freemail.ru>
Sent: Thu, 4/2/2009 10:18am
To: users_at_subversion.tigris.org
Subject: Re: Need advice: svnadmin dump and load between different versions of subversion?

Greetings, Timothy Kallinis!

TK> I need to filter out some modules from a fairly large svn repo running under Debian Sarge. The version of subversion is 1.1.4. I am able to perform "svnadmin dump repo", "svnfilter
TK> --renumber-revs --drop-empty-revs" successfully. However, I cannot load the dump file into an empty repo. I don't recall the exact error, but I believe it was "transaction not found" or something
TK> similar.

TK> As a test, I setup a Debian Lenny environment running subversion 1.5.1. I made a backup copy of the svn repo from the Debian sarge environment into the Lenny one and performed the following
TK> operations:

TK> svnadmin --pre-1.4-compatible --fs-type fsfs create svn-old-format
TK> svnadmin dump svn-back > svn-back.dump (Note that svn-back is a copy of the repo running under svn 1.1.4)
TK> cat svn-back.dump | lengthy svndumpfilter command > svn-filtered.dump
TK> cat svn-filtered.dump | svnadmin load svn-old-format

TK> This works perfectly fine in my Lenny chroot under svn 1.5.1. Can I now copy the repo I generated into the old Debian Sarge environment and expect svn 1.1.4 to work with it without any data
TK> corruption or other problems? Is this safe to do and are there any tests I can perform to verify data integrity? Perhaps, this is something that should never be done between such differing
TK> versions of subversion. I just don't know.

TK> Although I would dearly love to upgrade the Debian Sarge server to Debian Lenny, I will not be allowed to do this. However, I also need to filter out some modules and the only way that seems to
TK> work is the approach detailed above. There are huge differences between 1.1 and 1.5, so any advice would be appreciated.

TK> Subversion is installed from the standard Debian packages. BTW this is a production repo of a large size, about 15 GB.

Can you recompile 1.5 or 1.6 under your working server?
That would be much better solution.

--
WBR,
 Andrey Repin (anrdaemon_at_freemail.ru) 02.04.2009, <18:17>
Sorry for my terrible english...
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1519448
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].