It's nice to see that the OS where CentOS gets its sources from also experiments the same error! I have been very busy lately so I haven't had the time to deal with the problem, probably later this week or early next week. As soon as I find something Ill let you know. Hopefully you'll do the same if you come across the solution first. PS. Forwarding this message to the mailing list. Yvan Bourquin wrote: > Hello, > > I have exactly the same problem that you described below. > (On a RedHat Enterprise Linux system though) > Did you find a solution / workaround ? > Any information would be greatly appreciated ! > I look forward for your answer, > Cheers, > > Yvan > > > > Here is my problem, > > On my network there is a subversion server to which everybody connects > to and checks in/out code and documents. The workstations on the network > are all based on Fedora core 3. And everybody's home directory is on a > nfs share. This nfs share is mounted via the fstab. So no matter to > which box a user logs in, his/her home dir is gonna be the same. > > Now here is the trick. I installed a new CentOS4.3 workstation for > testing purposes. Mounted the home dirs like all the Fedora boxes. But > whenever I try to do svn update or any other subversion command from my > home dir I get the following: > > *Code:* > > bash-3.00$ svn update > > svn: REPORT request failed on '/svn/code/!svn/vcc/default' > > svn: REPORT of '/svn/code/!svn/vcc/default': 400 Bad Request > (https://subversion) > > bash-3.00$ > > But if I create a new directory, lets call it /local and I move there, > then I can check out code and docuemts and do everything else. > > Any ideas? > > Thanks > > Jean >