RE: help with repo upgrade?
From: Baker, Randy (US) (Contractor) <randy.baker_at_baesystems.com>
Date: Thu, 3 Aug 2017 11:10:07 +0000
Thank you for the speedy reply, and Yes, on purpose. I didn't think the list could benefit from the language in my last email. So, if I may more thoroughly explain : I'm a new hire here at this firm, tasked with upgrading the Subversion server from RHEL 5x to 7x. That was done successfully, but a user suggested I also upgrade the repos as well to benefit from the new server's features. The current server (from which I ran 'svnadmin upgrade') is 1.6.11. At the time, it was the only management server connected to NetApp (repos). Now, when users attempt any svn work, they get the error I reported in the ticket. So, now that I've added the new Subversion server (running 1.9.4) as a management server to NetApp, what should be my next move?
Should I want to just do 'svnadmin upgrade <repo>' from the new server, or do I need to dump and load the repos first? I have 200 repos, all production, so I'm sure you understand the need for accuracy here. Apologies for being such a newbie with this, but I'm being as cautious and informed as necessary. Thank you.
*** WARNING ***
On Thu, Aug 03, 2017 at 10:22:57AM +0000, Baker, Randy (US) (Contractor) wrote:
You forget to the Cc the list. Was this on purpose?
It does not matter which version you are using today.
This repository can only be salvaged by installing that old alpha release and dumping the repository with that release. This dump file can then be used with 1.9. This is what the link provided is supposed to explain.
This is an archived mail posted to the Subversion Users mailing list.