Re: Subversion 1.8.9 repository access issue [Urgent]
On Tue, May 20, 2014 at 12:02:23AM +, Mohsin Abbas wrote: > Team, > > I have installed latest subversion 1.8.9 to Linux machine and imported > repositories from old server. Actually I have moved my svn from one machine > to another machine on old machine svn 1.4.2 was installed and repositories > were created with svn 1.4.2 version . Now when I access repositories from > new server URL I am getting permission denied [403] error. I have copied > same configurations from old server to new server but on new svn server > repositories which were created with svn 1.4.2 are not working . Here I am > sharing some logs portion when I hit url . > > *[Mon May 19 21:52:25 2014] [debug] > subversion/mod_authz_svn/mod_authz_svn.c(400): [client ** x.x.x.x* > > *] Path to authz file is > /usr/local/apache/conf/extra/authz_svn_ITOPS.conf[Mon May 19 21:52:25 2014] > [error] [client x.x.x.x] Failed to load the mod_authz_svn config: Section > name 'Devices:/Trunk/' contains non-canonical fspath '/Trunk/'[Mon May 19 > 21:52:25 2014] [error] [client x.x.x.x] Access denied: 'mabbas' GET > MCP:/Trunk/OLTPJ/Documents/* Try removing the trailing slash. Use 'Devices:/Trunk', not 'Devices:/Trunk/'. > One more point which I want to ask for subversion 1.8.9 I have to use > latest svn client tortoise SVN 1.8 or 1.7 or 1.6 client can be used for > repository access? Yes, any 1.x client can talk to any 1.y server. There is more information about this here: http://subversion.apache.org/docs/release-notes/1.8.html#compatibility
Re: Subversion 1.8.9 repository access issue [Urgent]
Sir , Thanks for your quick response. Here i want to ask question in my previous server with subversion 1.4.2 this trailing slash works fine as i had already mentioned in my first email i copied same configurations which are working absolutely fine with subversion 1.4.2 why this is not working with subversion 1.8.9 either this is some limitations in new svn version ? or some other issue ? Regards
Re: Subversion 1.8.9 repository access issue [Urgent]
On Tue, May 20, 2014 at 03:13:45PM +0500, Mohsin Abbas wrote: > Sir , > > Thanks for your quick response. > Here i want to ask question in my previous server with subversion 1.4.2 > this trailing slash works fine as i had already mentioned in my first email > i copied same configurations which are working absolutely fine with > subversion 1.4.2 why this is not working with subversion 1.8.9 either this > is some limitations in new svn version ? or some other issue ? > > Regards I don't know exactly why this was changed. It's possible that this change in behaviour was intentional. It might have been this change: http://svn.apache.org/r1037662 The tests added there treats the path "/a/" as invalid, so your the path "Devices:/Trunk/" you use in the authz file is now also invalid.
Re: Subversion 1.8.9 repository access issue [Urgent]
Sir , That's make a sense I'll try this today and get back to you . Thank you for your support. Regards Mohsin On Tue, May 20, 2014 at 4:34 PM, Stefan Sperling wrote: > On Tue, May 20, 2014 at 03:13:45PM +0500, Mohsin Abbas wrote: > > Sir , > > > > Thanks for your quick response. > > Here i want to ask question in my previous server with subversion 1.4.2 > > this trailing slash works fine as i had already mentioned in my first > email > > i copied same configurations which are working absolutely fine with > > subversion 1.4.2 why this is not working with subversion 1.8.9 either > this > > is some limitations in new svn version ? or some other issue ? > > > > Regards > > I don't know exactly why this was changed. > It's possible that this change in behaviour was intentional. > > It might have been this change: http://svn.apache.org/r1037662 > The tests added there treats the path "/a/" as invalid, so your the path > "Devices:/Trunk/" you use in the authz file is now also invalid. >
Cannot add new file, but I can modify file
I just upgrade to apache 2.2.27 and now adding new file in SVN does not work. When I revert back to apache 2.2.25, adding the file works. Here is part of the error svn: Repository moved temporarily . please relocate svn: PROPFIND request failed on Here is part of my apache logs. [20/May/2014:09:56:40 -0400] "OPTIONS /svn/atg/cds-mas-parent/trunk/grads HTTP/1.1" 401 401 [20/May/2014:09:56:40 -0400] "OPTIONS /svn/atg/cds-mas-parent/trunk/grads HTTP/1.1" 200 - [20/May/2014:09:56:40 -0400] "PROPFIND /svn/atg/cds-mas-parent/trunk/grads HTTP/1.1" 207 726 [20/May/2014:09:56:41 -0400] "PROPFIND /svn/atg/!svn/vcc/default HTTP/1.1" 207 399 [20/May/2014:09:56:41 -0400] "PROPFIND /svn/atg/!svn/bln/1992 HTTP/1.1" 207 414 [20/May/2014:09:56:41 -0400] "OPTIONS /svn/atg/cds-mas-parent/trunk/grads HTTP/1.1" 200 187 [20/May/2014:09:56:41 -0400] "MKACTIVITY /svn/atg/!svn/act/4e7aeb19-4601-0010-95e4-f36ffe836761 HTTP/1.1" 201 226 [20/May/2014:09:56:41 -0400] "PROPFIND /svn/atg/cds-mas-parent/trunk/grads HTTP/1.1" 207 457 - [20/May/2014:09:56:41 -0400] "PROPFIND /svn/atg/!svn/vcc/default HTTP/1.1" 207 399 [20/May/2014:09:56:41 -0400] "CHECKOUT /svn/atg/!svn/bln/1992 HTTP/1.1" 201 243 [20/May/2014:09:56:41 -0400] "PROPPATCH /svn/atg/!svn/wbl/4e7aeb19-4601-0010-95e4-f36ffe836761/1992 HTTP/1.1" 207 462 [20/May/2014:09:56:41 -0400] "PROPFIND /svn/atg/cds-mas-parent/trunk/grads HTTP/1.1" 207 437 - [20/May/2014:09:56:41 -0400] "CHECKOUT /svn/atg/!svn/ver/1991/cds-mas-parent/trunk/grads HTTP/1.1" 201 265 - [20/May/2014:09:56:41 -0400] "PROPFIND /svn/atg/cds-mas-parent/trunk/grads/diff2.gs HTTP/1.1" 302 231 - [20/May/2014:09:56:41 -0400] "PROPFIND /svn/atg/!svn/wrk/4e7aeb19-4601-0010-95e4-f36ffe836761/cds-mas-parent/trunk/grads/diff2.gs HTTP/1.1" 302 231 Not sure where to look on this. Need some guidance. Thanks ~todd
Incorrect error message on svn copy? Advice?
Hi, I'm wondering if I'm getting an incorrect error message... I'm attempting to copy a file from a working copy to the server, but using an incorrect case for one of the folders in the path. The paths all exist and everything works fine using correct case. In the example below, "FOO" exists on the server as "foo". (Case 1) c:\Project_files\sandbox>svn copy bar.c http://svr/repo/some_project/FOO/bar.c -m "text commit" Adding copy ofbar.c svn: E155011: Commit failed (details follow): svn: E155011: File 'C:\Project_files\sandbox\bar.c' is out of date svn: E160013: File not found: transaction '4249-3lp', path '/some_project/FOO/bar.c' If I correctly use "foo" instead of "FOO", I get the expected response: (Case 2) c:\Project_files\sandbox>svn copy bar.c http://svr/repo/some_project/foo/bar.c -m "test commit" Adding copy ofbar.c Committed revision 4249. If I use --parents to create the path (in case it doesn't exist): (Case 3) c:\Project_files\sandbox>svn copy --parents bar.c http://svr/repo/some_project/FOO/bar.c -m "test commit" Adding copy ofbar.c svn: E165001: Commit failed (details follow): svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output: ** ERROR-CASE: This repository is set to be case insensitive. ** ERROR-CASE: Clash: '/some_project/FOO' '/some_project/foo' It appears we are using a server-side script to prevent name clashes (since we are using windows clients) on our server in Case 3. Why would Case 3 get caught (--parents) but Case 1 seem to slip by this server side script and return a different error? I assume we're using the stock case-insensitive.py, but regardless, I don't understand the behavior difference. As I would expect, I cannot perform an "svn info" on the incorrect-cased path. I was hoping I could do an "svn info" to test/determine what the case corrected path is, but will have to try an "svn copy --parents" first and if it fails due to a case clash, retry with the returned clash info. Is there a better way to accomplish this? I do understand this is more of a corner use case, especially since Subversion is (properly IMO) designed around case sensitivity. Thanks, Dan
Re: Subversion 1.8.9 repository access issue [Urgent]
Hello Sir, 403 permission denied issue has been resolved after removing trailing slash. Thanks for help. Now one more issue i am facing when i access repositories URL in Tortoise SVN client it gives unable to parse error [207 response code used with WEBDAV protocol]. But old svn 1.4.2 repositories are accessible with same Tortoise SVN but when I import 1.4.2 repositories in new svn 1.8.9 following error occurred. FYI SVN Client : TortoiseSVN 1.6.7 When I hit the URL in browser all data display correctly but in tortoise svn client 207 displays. In Apache error log: x.x.x.x - mabbas [21/May/2014:00:52:02 -0400] "PROPFIND /svn/x/x/!svn/vcc/default HTTP/1.1" *207* 467 x.x.x.x - mabbas [21/May/2014:00:52:02 -0400] "PROPFIND /svn/x/Ix/!svn/bc/24446/Trunk/Source/JavaAGI/docs HTTP/1.1" *207 *449 x.x.x.x - mabbas [21/May/2014:00:52:02 -0400] "PROPFIND /svn/x/x/!svn/bc/24446/Trunk/Source/JavaAGI/docs HTTP/1.1" *207 *3858 On Tue, May 20, 2014 at 11:34 AM, Stefan Sperling wrote: > On Tue, May 20, 2014 at 03:13:45PM +0500, Mohsin Abbas wrote: > > Sir , > > > > Thanks for your quick response. > > Here i want to ask question in my previous server with subversion 1.4.2 > > this trailing slash works fine as i had already mentioned in my first > email > > i copied same configurations which are working absolutely fine with > > subversion 1.4.2 why this is not working with subversion 1.8.9 either > this > > is some limitations in new svn version ? or some other issue ? > > > > Regards > > I don't know exactly why this was changed. > It's possible that this change in behaviour was intentional. > > It might have been this change: http://svn.apache.org/r1037662 > The tests added there treats the path "/a/" as invalid, so your the path > "Devices:/Trunk/" you use in the authz file is now also invalid. >
Re: Upgrading SVN version to 1.8.9
On Thu, May 15, 2014 at 2:55 PM, Prakash Ananth wrote: > Hello User group: > > Need help.. We have SVN version 1.6.11 on CentOS Platform. > > How do I upgrade to Version 1.8.9. Is there a upgrade notes for SVN server > install. > > Thanks and appreciate your help. > > Pash My friend, I have already published updated SRPM building tools. at https://github.com/nkadel/subversion-1.8.x-srpm/ I've been trying to publish them at Repoforge, but Repoforge seems to be moribund. Variouos companies, like Wandisco, publish freee binary packages for personal use. They're very useful to get up and running with the latest version, and they also publish very nice commercial tools that do commercial grade multi-master support.
