No apology necessary. Thanks for the prompt and informative responses. Now
to weigh my options....
> -----Original Message-----
> From: firstname.lastname@example.org [mailto:email@example.com]On
> Behalf Of firstname.lastname@example.org
> Sent: Monday, July 26, 2004 10:04 AM
> To: email@example.com
> Cc: firstname.lastname@example.org
> Subject: Re: hot-backup.py failed: Can't copy
> '/var/local/repositories/X' to '/var/local/backups/Y': File too large
> "Brian Fallik" <email@example.com> writes:
> > The comments provide more information, but I'm still unsure
> what the next
> > steps are for us to restore our backup process. Do I follow Joe Orton's
> > comment and assume it's fixed in the Linux build?
> > Do I need to rebuild subversion from scratch with a new
> setting? Where do I
> > change this setting? In which version of subversion is the
> >2Gb file limit
> > fixed - only the APR branch? How can I be certain that branch
> is stable? I
> > previously installed svn via rpms, so I'm slightly hesitent to start
> > building a developer branch from scratch.
> I think you're going to need to build from source to fix this. You
> technically don't need the absolute latest Subversion to do it, but I
> would recommend using head of Subversion trunk right now. I'm not
> sure how far back before Subversion stops being able to take advantage
> of the new APR functionality...
> ... which brings me to the important point, that what you really need
> is probably a newer APR, I *think* maybe one of the 1.0.x candidates
> (that's an APR version number, not a Subversion number). Visit
> apr.apache.org and poke around.
> Sorry you got bit by this one. In the future, as new versions of both
> Subversion and APR become the norm, it won't be a problem, but right
> now, it will involve a bit of inconvenience for you.
> > Are there special build parameters/settings that are used to
> produce the RH9
> > RPMs? Or is it all defaults?
> I don't know.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Jul 26 17:40:44 2004