On Tue, Jul 25, 2017 at 9:00 PM, Mark Phippard wrote:
> On Tue, Jul 25, 2017 at 2:00 PM, Andy So wrote:
>>
>> We have an old subversion version 1.4.3 (r23084) running on Solaris.
>>
>> We would like to upgrade to use new hardware on Linux based OS (CentOS
>>
On Tue, Jul 25, 2017 at 2:00 PM, Andy So wrote:
> We have an old subversion version 1.4.3 (r23084) running on Solaris.
>
> We would like to upgrade to use new hardware on Linux based OS (CentOS 6.9),
> possibly version 1.8.x or 1.9.x
If you're bumping Subversion release to 1.8.x
Don't forget that svnadmin dump/load and svnsync don't preserve hook scripts or
other ancillary data that might be in your repository directory on the server,
so if you have hook scripts, authorization rules or other customizations, carry
those over to the new server manually. And of course any
>> Does anyone know how long it would take to export the repository of this
>> size? This will give us an estimate how long to schedule down time and cut
>> off time.
Svnsync is the easy option.
If you insist on doing a dump/load, then a) you can time a test run of a
dump/load, and b)
On 7/25/2017 11:00 AM, Andy So wrote:
We have an old subversion /version 1.4.3 (r23084) /running on Solaris.
We would like to upgrade to use new hardware on Linux based OS (CentOS
6.9), possibly version 1.8.x or 1.9.x
Our plan is to installed and configure the latest SVN on CentOS 6.9.
On Tue, Jul 25, 2017 at 2:00 PM, Andy So wrote:
> We have an old subversion *version 1.4.3 (r23084) *running on Solaris.
>
> We would like to upgrade to use new hardware on Linux based OS (CentOS
> 6.9), possibly version 1.8.x or 1.9.x
>
>
>
> Our plan is to installed and
We have an old subversion version 1.4.3 (r23084) running on Solaris.
We would like to upgrade to use new hardware on Linux based OS (CentOS 6.9),
possibly version 1.8.x or 1.9.x
Our plan is to installed and configure the latest SVN on CentOS 6.9. Then go
through dump and load of the repository
-Hi Bob,
First off, thank you very much for your quick reply.
We were running a 1.4.2 subversion server, and upgraded the subversion
server to 1.6.6. The clients have not changed in any way, and were a mix
of 1.4, 1.5 and 1.6 clients that used http only to communicate with
the subversion