Path not found

2012-12-23 Thread Gautier DI FOLCO
Hi all, I have a quite annoying problem, I use svn 1.6.15 with mod_dav on Apache HTTPd 2.2.8 on the server side and sevral clients. When I try to checkout on the same computer, it works, but on an other machine I have the following message: svn: E160013: '/svn/repo/!svn/vcc/default' path not found

Re: 200 OK error on update with files that contain non-alphanumeric characters

2012-10-24 Thread Gautier DI FOLCO
2012/10/24 Nico Kadel-Garcia > There's also my SRPM building patches and files at > http://github.com/nkadel/subversion-1.7.6-srpms/ and > subversoin-1.6.18-srpms/. I need to update those to 1.7.7 and 1.6.19: > they're what were used for the last updates at "rpmforge-extras", > which is noticeabl

Re: 200 OK error on update with files that contain non-alphanumeric characters

2012-10-20 Thread Gautier DI FOLCO
2012/10/19 Stefan Sperling > On Fri, Oct 19, 2012 at 06:18:43PM +0200, Gautier DI FOLCO wrote: > > I'm on CentOS 5.8, I can't upgrade svn any more :/ > > You can, see http://subversion.apache.org/packages.html#centos > The packages from Collabnet and Wandisco are adve

Re: 200 OK error on update with files that contain non-alphanumeric characters

2012-10-19 Thread Gautier DI FOLCO
2012/10/19 Ulrich Eckhardt > This looks weird, "200 OK" actually means "success"... That's why I'm a little bit unsettled. > Try "svn ls " to see the actual content. The problem could be > that you really checked in those files urlencoded by accident (I assume you > mean e.g. %20 instead of sp

200 OK error on update with files that contain non-alphanumeric characters

2012-10-19 Thread Gautier DI FOLCO
Hi all, I have a quite annoying problem, I use svn 1.6.15 with mod_dav on Apache HTTPd 2.2.8 on the server side and sevral clients. On the client side, when I add and commit a file which has spaces or non-ASCII characters, all works, but, if I try do do an update, I have the following error: Upda

Re: Forcing the association of the author

2012-10-15 Thread Gautier DI FOLCO
2012/10/16 Andy Levy > You cannot allow anonymous commits if you want to capture the > committer's name. IOW, you need to require authentication and that > requires that you prompt for a password (also, consider this: if you > don't enforce passwords, a malicious user can commit things to the > r

Forcing the association of the author

2012-10-15 Thread Gautier DI FOLCO
I have an SVN repository requestable via Apache HTTPD Server 2.2.8. I want to allow anyone to update or commit on it but I want a committer name. So I must force the clients to provide an username but I don't want to check his password. I try this: DAV svn SVNParentPath /www/sv