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

Re: Debian Linux 32 vs. 64 bit

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Tue, 26 Jan 2016 00:33:17 +0000

David Chapman <dcchapman_at_acm.org> writes:

> On 1/25/2016 10:45 AM, Philip Martin wrote:
>> It should just work for both repositories and working copies.
>
> Is that documented somewhere, such that system administrators can rely
> on it?

I don't know if it is explictly documented anywhere. The closest I can
get is:

http://svnbook.red-bean.com/nightly/en/svn.reposadmin.planning.html#svn.reposadmin.basics.backends.tbl-1

> Or could a Subversion developer decide to put endian- or
> size-dependent binary data into a repository or working copy file
> somewhere?

It happens but should be removed, for an example see
http://svn.apache.org/r1573371

> My notes are vague, unfortunately. This was back in 2007, when I was
> compiling from tarballs:
>
> 1) configure/compile with BDB support on both platforms
> 2) copy repository directory to 32-bit machine
> 3) problem found -> dump/load to avoid system dependencies
> 4) problem solved
> 5) hey, my repositories are actually FSFS!

The BDB data files are portable but the BDB environment files are
platform dependent. Switching platforms for BDB generally requires a
BDB recover operation to replace the BDB environment files, and may
require a BDB upgrade operation if the BDB library version changes.

FSFS repositories need no special operations.

-- 
Philip Martin
WANdisco
Received on 2016-01-26 01:33:31 CET

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.