Re: Debian Linux 32 vs. 64 bit
David Chapman 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
Re: Debian Linux 32 vs. 64 bit
On 1/25/2016 10:45 AM, Philip Martin wrote: David Chapman writes: On 1/25/2016 3:59 AM, Niemann, Hartmut wrote: I want to upgrade my Linux box from Debian Jessie (32bit) to Debian Jessie (64bit). For the transition time, the machine will boot alternating the 32bit and the 64bit OS. I have several SVN repositories and working copies on it. Is it safe to share SVN repositories and working copies between 32bit and 64 bit? (Jessie ships with 1.8.10, as far as I know.) It should just work for both repositories and working copies. Is that documented somewhere, such that system administrators can rely on it? Or could a Subversion developer decide to put endian- or size-dependent binary data into a repository or working copy file somewhere? I wouldn't try this approach for a machine with repositories. I had a repository on a 64-bit Linux machine, then bought a 32-bit micro server that I could keep running all the time. I was unable to copy the repository directory tree directly, even though both were Intel architecture machines. I had to dump and load (with svnadmin). I'd be surprised if this has changed in the last three years. It's hard to work out what went wrong from that vague description. In the unlikely event that you were using a BDB repository then there are BDB library compatibility issues: a recover/upgrade may be needed and downgrading to older BDB is not always possible. 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! I was trying to take good notes, as is my practice for system administration tasks that I do once every three years, but somewhere in the migration process I failed to write something down. Item 5) was recorded some weeks after the migration, so I don't know when the build switched to FSFS support only, relative to the repository directory move. Nor do my notes record what actually got me to a production-worthy repository. So yes, kind of vague. But enough to get me spooked. I also know from experience that it is very easy to let platform dependencies leak into outside data files. Avoidance takes a concerted effort and detection is extremely difficult when testing a build on a single machine (here, by definition we're talking about running a single repository on two separate machines). Thus my question about a documented promise from Subversion developers. -- David Chapman dcchap...@acm.org Chapman Consulting -- San Jose, CA Software Development Done Right. www.chapman-consulting-sj.com
Re: Debian Linux 32 vs. 64 bit
David Chapman writes: > On 1/25/2016 3:59 AM, Niemann, Hartmut wrote: >> >> I want to upgrade my Linux box from Debian Jessie (32bit) to Debian >> Jessie (64bit). >> >> For the transition time, the machine will boot alternating the 32bit >> and the 64bit OS. >> >> I have several SVN repositories and working copies on it. >> >> Is it safe to share SVN repositories and working copies between >> 32bit and 64 bit? >> >> (Jessie ships with 1.8.10, as far as I know.) It should just work for both repositories and working copies. > I wouldn't try this approach for a machine with repositories. I had a > repository on a 64-bit Linux machine, then bought a 32-bit micro > server that I could keep running all the time. I was unable to copy > the repository directory tree directly, even though both were Intel > architecture machines. I had to dump and load (with svnadmin). I'd > be surprised if this has changed in the last three years. It's hard to work out what went wrong from that vague description. In the unlikely event that you were using a BDB repository then there are BDB library compatibility issues: a recover/upgrade may be needed and downgrading to older BDB is not always possible. -- Philip Martin WANdisco
Re: Debian Linux 32 vs. 64 bit
On 1/25/2016 3:59 AM, Niemann, Hartmut wrote: Hello! I want to upgrade my Linux box from Debian Jessie (32bit) to Debian Jessie (64bit). For the transition time, the machine will boot alternating the 32bit and the 64bit OS. I have several SVN repositories and working copies on it. Is it safe to share SVN repositories and working copies between 32bit and 64 bit? (Jessie ships with 1.8.10, as far as I know.) I wouldn't try this approach for a machine with repositories. I had a repository on a 64-bit Linux machine, then bought a 32-bit micro server that I could keep running all the time. I was unable to copy the repository directory tree directly, even though both were Intel architecture machines. I had to dump and load (with svnadmin). I'd be surprised if this has changed in the last three years. It is possible that the working copies would be OK, but I haven't tried that migration path. I'd worry that there are binary files in the working copy format as well (e.g. SQLite), and these might have native long integers which will switch from 32 to 64 bits on Linux machines. I just did a 32-bit to 32-bit migration, and I found that the safest approach was to have a separate machine (or at least a separate hard drive) so that I always had a stable system running. I took the original offline only after the new one was running and stable. -- David Chapman dcchap...@acm.org Chapman Consulting -- San Jose, CA Software Development Done Right. www.chapman-consulting-sj.com
Debian Linux 32 vs. 64 bit
Hello! I want to upgrade my Linux box from Debian Jessie (32bit) to Debian Jessie (64bit). For the transition time, the machine will boot alternating the 32bit and the 64bit OS. I have several SVN repositories and working copies on it. Is it safe to share SVN repositories and working copies between 32bit and 64 bit? (Jessie ships with 1.8.10, as far as I know.) Mit freundlichen Grüßen Dr. Hartmut Niemann Siemens AG MO MLT LM EN CCI 1 Werner-von-Siemens-Str. 67 91052 Erlangen, Deutschland Tel.: +49 9131 7-34264 Fax: +49 9131 7-26254 mailto:hartmut.niem...@siemens.com Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Gerhard Cromme; Vorstand: Joe Kaeser, Vorsitzender; Roland Busch, Lisa Davis, Klaus Helmrich, Janina Kugel, Siegfried Russwurm, Ralf P. Thomas; Sitz der Gesellschaft: Berlin und München, Deutschland; Registergericht: Berlin Charlottenburg, HRB 12300, München, HRB 6684; WEEE-Reg.-Nr. DE 23691322
