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

Re[2]: Need advice: svnadmin dump and load between different versions of subversion?

From: Andrey Repin <anrdaemon_at_freemail.ru>
Date: Thu, 2 Apr 2009 20:44:18 +0400

Greetings, Timothy Kallinis!

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

I don't know SVN codebase, I can only assume, as I don't see any python-specific
libraries in SVN 1.6 binary distribution, it does not need it to run.
May be Python scripts need at compile time... I don't know.

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

Sorry, I can't answer your question... Your best bet is just try it, copy to
your server as separate directory and run as many tests as you only can
invent. Property editing, commit (especially - import into the root of
repository), checkout, diff...

--
WBR,
 Andrey Repin (anrdaemon_at_freemail.ru) 02.04.2009, <20:38>
Sorry for my terrible english...
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1521108
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-02 18:59:54 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.