Re: Upgrade to CentOS 4.3 breaks subversion

Hi,

 The repository is FSFS and its been working fine for over a year. Its
just now that I've upgraded some workstations to 4.3 that Working Copies
on NFS are throwing this error.

Thanks for the reply,
Greg

On Wed, 2006-03-22 at 17:00 +0100, Ryan Schmidt wrote:
> On Mar 22, 2006, at 15:49, Greg Dickie wrote:
>
> >> I've just updated a build machine to CentOS 4.3 and suddenly
> >> subversion is busted. Has anyone else seen this in RHEL 4.3?
> >> Subversion
> >> itself was not updated but apr was. I tried reverting it and it
> >> did not
> >> help. I realize this is not strictly a subversion problem but if
> >> anyone
> >> could give me a hint as to how to find the problematic RPM it
> >> would be
> >> most appreciated.
> >>
> >> The error I now get is:
> >>
> >> [greg@edinburgh lvm2]$ svn up
> >> svn: REPORT request failed on '/packages/!svn/vcc/default'
> >> svn: REPORT of '/packages/!svn/vcc/default': 400 Bad Request
> >> (http://svn)
> >
> > Bad form replying to my own posting but since no one seems to have
> > seen
> > this, here is some more information.
> >
> > If the WC is on an NFS mount is you get the error. If its local, it
> > works fine. Building the srpm fails a bunch of tests on the 4.3
> > machine
> > as well. Didn't try building it on a local disk. Can anyone see why
> > NFS
> > would be a problem? Any way to debug this further?
>
> You did not specify whether you're using a BDB repository or an FSFS
> one. BDB repositories are known to blow up when placed on NFS
> volumes. FSFS repositories should work fine there.
>
>

-- 
Greg Dickie
just a guy
Maximum Throughput
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org