Re: Migration from CentOS 7, Subversion 1.94 to Ubuntu 24.04, SVN 1.14.3

Once again thanks for all your past help

The new repository is up and running. But we haven't cut over yet.

I have asked folks to commit all changes that they would like included 
in new repo.

I'm using svnsync multiple times per day, with no issues.

There's a good chance that DNS name may not be able to stay the same.

TortoiseSvn is used almost exclusively for commits. and checkouts.

If I try a relocate in TortoiseSVN, I get an error saying the uuid of 
the new server is different than the WC of the local repo.   I presume 
this is because of the DNS name change.

I've done some searching and have followed a suggestion and edited the 
wc.db and replaced old server uuid with new server uuid, tried the 
relocate command again and things seem to be working and pointing to new 
server.

I also know that doing a new checkout from the new server may be the 
simplest solution. But perhaps some folks will not commit all of their 
changes before switchover because they are not ready.

The reason I am posting here instead of TortoiseSVN is I would like to 
know whether it would be safer to have folks just do a new checkout from 
new server once old server is shutdown, (and diff folders if needed) 
instead of trying relocate, or should I have them edit the wc.db and 
replace or try and change the uuid on the new server to match the old one.

I've done some reading in the SVN-redbook, but am concerned that perhaps 
there are things that I may be missing because the redbook may be out of 
date.

I've also read of some issues of changing uuid on server, so if that is 
what should be done, I would like specific instructions/suggestions.

Thanks,

Paul

On 6/7/2024 10:17 AM, Paul Leo wrote:
>
> Tak Daniel.
>
> Appreciate the detailed response.  I have asked for the two hooks that 
> seemed to be copied from the templates.
>
> If the dump doesn't work, I may have them try and tar up the whole 
> repo directory.
>
> I do have the auth tables, and will try them once repo is up and 
> running, otherwise, I will create new user/passwords.  The community 
> is small enough so that this should not be an issue.
>
> On 6/7/2024 2:16 AM, Daniel Sahlberg wrote:
>> Den tors 6 juni 2024 kl 21:40 skrev Paul Leo 
>> <[email protected]>:
>>
>>     We need to migrate an SVN repository from CentOS 7, Subversion
>>     1.94 to
>>     Ubuntu 24.04, SVN 1.14.3.
>>
>>     We don't have any login access to the current server.
>>
>>     The current hosting server plans to perform an SVN dump of the
>>     repository, and make it available through something like Google
>>     Drive.
>>
>>     We would obtain the dump file and then use svnadmin load,
>>     importing the
>>     repository.
>>
>>
>> As others have already pointed out svnadmin dump/load or svnrdump are 
>> the main candidates. Another option is to have your hosting provider 
>> pack the repository folder in its entirety (to a tar.gz) which you 
>> could unpack on the new server and use as-is.
>>
>>
>>     There are only a few hooks that are currently used.  The main one
>>     being
>>     to force a commit message when committing.
>>
>>
>> Although the dump file does NOT contain any hook scripts. These need 
>> to be extracted from the [/path/to/repo]/hooks directory on the 
>> server. If you don't have access to the server yourself (and the 
>> hosting provider doesn't have a web interface to manage the hook 
>> scripts) you need to ask them to copy the scripts manually. (If your 
>> hosing provider choose to pack the complete repository folder the 
>> hooks are of course included).
>>
>>
>>     We will use Apache httpd and basic authentication for committing to
>>     repository, as in done currently
>>
>>
>> The authentication (login) and authorization (permissions) are not 
>> included in the dump file either. If you want to keep the 
>> username/passwords the hosting provider need to give you these files 
>> as well (path and filename depends on the setup in Apache httpd).
>>
>>
>>     We would change DNS to new server IP.
>>
>>
>> I assume you mean you use a DNS entry 
>> (https://svn.example.com/repos/.. 
>> <https://svn.example.com/repos/..>.) which will be updated. In this 
>> case you should not need to do anything. If you change some part of 
>> the URL (either new hostname, adding SSL/TLS or the path to the 
>> repositories) you need to run
>>
>> svn relocate [new_url]
>>
>> in each working copy.
>>
>>
>>     I've read through the svnbook, and the above seems plausible.
>>
>>     I am just wondering if anyone has some guidance and suggestions,
>>     since
>>     we are making a significant jump to newer version of SVN.
>>
>>
>> There should be no major difference.
>>
>>
>>     Thanks for your help
>>
>>
>> Kind regards,
>> Daniel