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

Re: svnadmin dump | svnadmin load breaks peg revisions?

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Thu, 06 Aug 2009 17:12:26 -0500

Dan Stromberg wrote:
>>> 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.

I'm not one of the developers and can't fix anything, but I don't
remember seeing anyone acknowledge that your situation should exist in
the first place. So I'd say the first step should be to try what you
did again and test peg revision access.

>> 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 didn't mean what was shipped with the OS, I meant whatever the current
update gets you. But if that's a 1.4.x I'd look for something newer
even if you have to build it yourself.

> 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.

Is the subversion server a build host too? Even so, I don't think I'd
want to keep using a 1.4.x.

> 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 (?).

I'd think you'd want to run a fairly current 64-bit version going
forward. You just need to avoid whatever it was that broke your access
to peg revisions in the process of converting.

   Les Mikesell
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-07 00:13:37 CEST

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.