On Thu, Aug 6, 2009 at 1:26 PM, Les Mikesell<lesmikesell_at_gmail.com> wrote:
> Dan Stromberg wrote:
>>
>>>
>>>> That is, is a host to host tar copy of an FSFS repo a good way of
>>>> getting exactly the same stuff on another system?
>>>
>>> Only if they are running the same version of Subversion, the same
>>> operating
>>> system, and have the same type of processor.
>>>
>>>
>>
>> They both have the same release number of subversion installed on them.
>>
>> The old server has CentOS 4.6. The new server has openSUSE 10.3.
>>
>> The old server is an x86-64 system running an x86 OS. The new server
>> is an x86-64 system runnnig an x86-64 OS. So there's a bit of a
>> difference.
>>
>> Is it at all likely that this is close enough that I could just tar | ssh
>> tar?
>>
>> Does an FSFS repo generally have word size and/or endianness details
>> in it? (FWIW:
>> http://stromberg.dnsalias.org/~strombrg/converting-binary.html)
>>
>> Is svnadmin dump | ssh svnadmin load supposed to just convert to an
>> architecture neutral format and back to a native representation, or is
>> there more to it than that?
>>
>> I could make the x86-64 system use a 32 bit subversion if that'd help.
>
> I don't think I saw an explanation for the problem you are seeing and this
> doesn't sound like the best solution even if it happens to work.
I'm on a pretty fixed timeline, but if you believe you can lick
whatever bug it is I'm seeing within about 15 calendar days, I suppose
I can go for that.
> Can you try the dump/load into a more recent subversion (preferably the
> latest for your OS distro so it will be easy to keep up to date) to see if
> that fixes the peg revision issue? If it does, that would be a better base
> to do whatever you have to do to back in the subsequent updates.
Both OS's appear to come with the same version of subversion, though
who knows how many patches the distributors have applied relative to
your upstream, and if there are any, there's a pretty good chance they
aren't the same patches. I doubt either OS is the latest from their
respective distributors - we need an old OS on our build hosts for
compatibility with our product. I can likely compile the latest
subversion on the 32 bit system and copy it over to the 64 bit system
for testing, to avoid compiling a 32 bit subversion on a 64 bit
system... It'd probably be easiest to do this under
/usr/local/svn/{bin,lib} or similar, copy, and symlink - if there
aren't any hardcoded paths in the resulting executables (?).
Thanks for being interested in the issue.
> --
> Les Mikesell
> lesmikesell_at_gmail.com
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2381080
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-06 23:20:24 CEST