Alas thats a bit tricky to do on a RedHat system and still keep things
sane. At least ES 5 is due out next month.
Alex.
On 7/30/06, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
>
> On 7/30/06, Alex Turner <armtuk@gmail.com> wrote:
> > Sorry - that might have been usefull:
> >
> > Client OS: RedHat ES 4 (Nahant Update 3), linux 2.6.9-34.EL.smp, svn
> 1.1.4
> > (r13838) on Dual CPU AMD Opteron
> >
> > Server OS: RedHat ES 4 (Nahant Update 3), linux 2.6.9-34 EL, svn 1.1.4
> > (r13838) on Single CPU Celeron, using svnserve to access remotely.
> >
> > (yeah the server is a POS compared to the client, long story to do with
> who
> > owns what and stuff).
>
> Well, considering that you're using a version of Subversion that's
> over a year old (and at least two minor version revs out of date) the
> first thing I'd recommend is updating to a more current version (1.3.x
> most likely, as it's the current release version) on both the client
> and server. If that doesn't fix the problem, I'd love to see if you
> can reproduce it with a 1.4.x release candidate, but it's a bit harder
> to recommend that if you can't reproduce it outside your production
> environment since it's not a real released version of svn.
>
> -garrett
>
Received on Mon Jul 31 03:53:34 2006