Subversion Client on z/OS
Hello Does anyone succeed to run an SVN Client on z/os ? Is It possible to share binaries running under USS ? Any help would be appreciated Jean
Differences in authz handling between svn 1.6 and 1.7
We have been using a mixed authentication setup to allow configuration of anonymous access within authz files. When testing svn 1.7, we have found that using "satisfy any" in the httpd configuration but not granting anonymous read permissions in the authz file is preventing access by users with credentials as well. Sample configuration: httpd.conf: DAV svn SVNPath /var/svn SVNAutoversioning on AuthzSVNAccessFile /var/access/svn_authz AuthName "Subversion Login" AuthType Basic AuthUserFile /var/access/htpasswd Satisfy any Require valid-user svn_authz: [/] * = user = rw When running this configuration on a svn 1.6.x server, when a checkout is performed the user is prompted for a password and they are able to retrieve the full directory tree. With a svn 1.7.x server running the same configuration, the client is still prompted for a password, but then receives the error "svn: E22: Not authorized to open root of edit operation". In the server logs for svn 1.6.x, a checkout would show an initial OPTIONS request getting a 401 authentication request, then all subsequent requests would come in as the user: - - [11/Apr/2013:04:52:28 -0400] "OPTIONS /repo1 HTTP/1.1" 401 401 - testuser [11/Apr/2013:04:52:28 -0400] "OPTIONS /repo1 HTTP/1.1" 200 185 - testuser [11/Apr/2013:04:52:29 -0400] "PROPFIND /repo1 HTTP/1.1" 207 641 - testuser [11/Apr/2013:04:52:29 -0400] "PROPFIND /repo1/!svn/vcc/default HTTP/1.1" 207 392 - testuser [11/Apr/2013:04:52:29 -0400] "PROPFIND /repo1/!svn/bln/0 HTTP/1.1" 207 443 - testuser [11/Apr/2013:04:52:29 -0400] "PROPFIND /repo1 HTTP/1.1" 207 641 - testuser [11/Apr/2013:04:52:30 -0400] "PROPFIND /repo1/!svn/vcc/default HTTP/1.1" 207 443 - testuser [11/Apr/2013:04:52:30 -0400] "PROPFIND /repo1/!svn/bc/0 HTTP/1.1" 207 651 - - [11/Apr/2013:04:52:30 -0400] "OPTIONS /repo1 HTTP/1.1" 401 401 - testuser [11/Apr/2013:04:52:30 -0400] "OPTIONS /repo1 HTTP/1.1" 200 185 - testuser [11/Apr/2013:04:52:31 -0400] "PROPFIND /repo1 HTTP/1.1" 207 641 - testuser [11/Apr/2013:04:52:31 -0400] "PROPFIND /repo1 HTTP/1.1" 207 641 - testuser [11/Apr/2013:04:52:31 -0400] "PROPFIND /repo1/!svn/vcc/default HTTP/1.1" 207 392 - testuser [11/Apr/2013:04:52:31 -0400] "PROPFIND /repo1/!svn/bln/0 HTTP/1.1" 207 443 - testuser [11/Apr/2013:04:52:32 -0400] "REPORT /repo1/!svn/vcc/default HTTP/1.1" 200 604 In the server logs for svn 1.7.x, a checkout shows only one PROPFIND request being sent with credentials. All other requests do not have a username in the logs: - - [11/Apr/2013:04:50:47 -0400] "OPTIONS /repo1 HTTP/1.1" 200 185 - - [11/Apr/2013:04:50:47 -0400] "OPTIONS /repo1 HTTP/1.1" 200 185 - - [11/Apr/2013:04:50:48 -0400] "PROPFIND /repo1/!svn/rvr/0 HTTP/1.1" 401 401 - testuser [11/Apr/2013:04:50:48 -0400] "PROPFIND /repo1/!svn/rvr/0 HTTP/1.1" 207 652 - - [11/Apr/2013:04:50:48 -0400] "OPTIONS /repo1 HTTP/1.1" 200 185 - - [11/Apr/2013:04:50:48 -0400] "OPTIONS /repo1 HTTP/1.1" 200 185 - - [11/Apr/2013:04:50:49 -0400] "REPORT /repo1/!svn/me HTTP/1.1" 500 241 Using SVNParentPath instead of SVNPath does appears to work: - - [11/Apr/2013:05:02:38 -0400] "OPTIONS /parent/repo1 HTTP/1.1" 401 401 - testuser [11/Apr/2013:05:02:38 -0400] "OPTIONS /parent/repo1 HTTP/1.1" 200 192 - testuser [11/Apr/2013:05:02:38 -0400] "OPTIONS /parent/repo1 HTTP/1.1" 200 192 - testuser [11/Apr/2013:05:02:38 -0400] "PROPFIND /parent/repo1/!svn/rvr/0 HTTP/1.1" 207 666 - - [11/Apr/2013:05:02:39 -0400] "OPTIONS /parent/repo1 HTTP/1.1" 401 401 - testuser [11/Apr/2013:05:02:39 -0400] "OPTIONS /parent/repo1 HTTP/1.1" 200 192 - testuser [11/Apr/2013:05:02:39 -0400] "OPTIONS /parent/repo1 HTTP/1.1" 200 192 - testuser [11/Apr/2013:05:02:40 -0400] "REPORT /parent/repo1/!svn/me HTTP/1.1" 200 593 Is this expected behavior with the current version of SVN, and are there any workarounds? We do have a virtual server set up for testing which is running both versions of SVN on different ports if it helps.
SVN/Tortoise error "assertion failed"
Hi all, Recently, I switched to TortoiseSVN-1.7, made an upgrade of the SVN working copy, and tried to run the first SVN update. I got the following error message. Is there any help around? Kind regards, Silvia Updating: C:\Users\stackelb\Desktop\Documents\Muhannad-SVN\PSE-SS-2013 Error: In file Error: 'D:\Development\SVN\Releases\TortoiseSVN-1.7.12\ext\subversion\subversion\libsvn_wc\update_editor.c' Error: line 1315: assertion failed (added_status == svn_wc__db_status_added || Error: added_status == svn_wc__db_status_copied || added_status == Error: svn_wc__db_status_moved_here) -- Dr.-Ing. Silvia von Stackelberg Am Fasanengarten 5, 76131 Karlsruhe / Gebäude 50.34 Raum 365 Tel. +49 721 608-47351 Karlsruher Institut für Technologie (KIT) Fakultät für Informatik Institut für Programmstrukturen und Datenorganisation (IPD) Lehrstuhl für Systeme der Informationsverwaltung KIT - Universität des Landes Baden-Württemberg und nationales Großforschungszentrum in der Helmholtz-Gemeinschaft
feature suggestion: add elements of repo browser to log window
I suggest adding the repo browser URL dropdown and tree to the log window, where to save real estate it could for example show the tree in the URL dropdown or have a Show Tree button. I initially didn't understand why certain versions were missing from the log and tried to solve it while staying on the log window. If there had been a dropdown or button there I surely would have looked at it. Don
Re: feature suggestion: add elements of repo browser to log window
On Thu, Apr 11, 2013 at 10:29:32AM -0700, Don Stock wrote: > I suggest adding the repo browser URL dropdown and tree to the log window, > where to save real estate it could for example show the tree in the URL > dropdown or have a Show Tree button. > > I initially didn't understand why certain versions were missing from the log > and tried to solve it while staying on the log window. If there had been a > dropdown or button there I surely would have looked at it. > > Don Hi Don, this list is about Apache Subversion which only has a command line interface. It sounds like you are talking about a third-party GUI interface for Subversion but I cannot recognize which of the various GUIs that exist you might be talking about. I'd suggest that you direct your request at the appropriate forum for the Subversion GUI software you are using.
Re: feature suggestion: add elements of repo browser to log window
On 04/11/2013 01:29 PM, Don Stock wrote: > I suggest adding the repo browser URL dropdown and tree to the log window, > where to save real estate it could for example show the tree in the URL > dropdown or have a Show Tree button. > > I initially didn't understand why certain versions were missing from the log > and tried to solve it while staying on the log window. If there had been a > dropdown or button there I surely would have looked at it. I'm guessing you've contacted the wrong mailing list. This list (users@subversion.apache.org) is for users of the Subversion core distribution, which includes command-line utilities only (nothing GUI-like). As such, we don't have "dropdowns", "windows", etc. Perhaps you meant to contact the us...@tortoisesvn.tigris.org list instead? -- C. Michael Pilato CollabNet <> www.collab.net <> Enterprise Cloud Development signature.asc Description: OpenPGP digital signature
Re: feature suggestion: add elements of repo browser to log window
Wrong number. You should send these suggestions to the TortoiseSVN project, not to Apache Subversion (of which TortoiseSVN is but one client). Daniel Don Stock wrote on Thu, Apr 11, 2013 at 10:29:32 -0700: > I suggest adding the repo browser URL dropdown and tree to the log window, > where to save real estate it could for example show the tree in the URL > dropdown or have a Show Tree button. > > I initially didn't understand why certain versions were missing from the log > and tried to solve it while staying on the log window. If there had been a > dropdown or button there I surely would have looked at it. > > Don
Subversion Ruby Binding: Server certificate verification failed: issuer is not trusted
Hi, I have been trying for some hours to use the ruby subversion binding to do a repository checkout. Unfortunately, the server certificate is not accepted: $ /.../script.rb /usr/lib/ruby/site_ruby/1.9.1/svn/util.rb:99:in `svn_client_checkout3': (Svn::Error::RaDavRequestFailed) Svn::Error::RaDavRequestFailed: OPTIONS of 'https://...': Server certificate verification failed: issuer is not trusted (https://...) from /usr/lib/ruby/site_ruby/1.9.1/svn/util.rb:99:in `checkout3' from /usr/lib/ruby/site_ruby/1.9.1/svn/client.rb:143:in `checkout' from /.../script.rb:22:in `' Using the SVN client from command line I never faced any certificate issues (as far as I know the certificate is perfectly valid). However, I started looking for a way to make the ruby script accept the certificate. As to my knowledge there is no documentation for the ruby binding, so I looked into the ruby files of the ruby binding and into the documentation of the C binding but I could not find a solution. The script (see below) is taken from the best piece of documentation I could find in the web: http://www.markdeepwell.com/2010/06/ruby-subversion-bindings/ Does anyone know how to deal with this problem? Kind regards Christian PS: Please put me into CC as I am not subscribed to the list. Thanks! My ruby script: #!/usr/bin/env ruby # Required packages require "svn/core" require "svn/ext/core" require "svn/client" require "svn/wc" require "svn/repos" config_username = '...' config_password = '...' config_repository_url = '...' config_output_path = '...' config_revision = 1 ctx = Svn::Client::Context.new() ctx.add_simple_provider ctx.auth_baton[Svn::Core::AUTH_PARAM_DEFAULT_USERNAME] = config_username ctx.auth_baton[Svn::Core::AUTH_PARAM_DEFAULT_PASSWORD] = config_password begin ctx.checkout(config_repository_url, config_output_path, config_revision.to_i, nil) rescue Svn::Error::CLIENT_UNRELATED_RESOURCES => e # revision doesn't exist raise "no such revision " + revision.to_s + " at " + repos_uri end
Re: Subversion Ruby Binding: Server certificate verification failed: issuer is not trusted
Christian Plewnia wrote on Thu, Apr 11, 2013 at 20:51:26 +0200: > Hi, > > I have been trying for some hours to use the ruby subversion binding to > do a repository checkout. Unfortunately, the server certificate is not > accepted: > > $ /.../script.rb > /usr/lib/ruby/site_ruby/1.9.1/svn/util.rb:99:in `svn_client_checkout3': > (Svn::Error::RaDavRequestFailed) > Svn::Error::RaDavRequestFailed: OPTIONS of 'https://...': Server certificate > verification failed: issuer is not trusted (https://...) > from /usr/lib/ruby/site_ruby/1.9.1/svn/util.rb:99:in `checkout3' > from /usr/lib/ruby/site_ruby/1.9.1/svn/client.rb:143:in `checkout' > from /.../script.rb:22:in `' > > Using the SVN client from command line I never faced any certificate > issues (as far as I know the certificate is perfectly valid). However, I > started looking for a way to make the ruby script accept the > certificate. As to my knowledge there is no documentation for the ruby > binding, so I looked into the ruby files of the ruby binding and into > the documentation of the C binding but I could not find a solution. > Look at svn_cmdline_create_auth_baton(). You need to pass trust_server_cert=TRUE (in C terms) or implement a prompt provider that answers affirmatively. (or reconfigure your SSL library to trust that certificate by default, in a level below Subversion) > The script (see below) is taken from the best piece of documentation I > could find in the web: > > http://www.markdeepwell.com/2010/06/ruby-subversion-bindings/ > > Does anyone know how to deal with this problem? > > Kind regards > Christian > > PS: Please put me into CC as I am not subscribed to the list. Thanks! > > My ruby script: > > #!/usr/bin/env ruby > > # Required packages > require "svn/core" > require "svn/ext/core" > require "svn/client" > require "svn/wc" > require "svn/repos" > > config_username = '...' > config_password = '...' > config_repository_url = '...' > config_output_path = '...' > config_revision = 1 > > ctx = Svn::Client::Context.new() > ctx.add_simple_provider > ctx.auth_baton[Svn::Core::AUTH_PARAM_DEFAULT_USERNAME] = config_username > ctx.auth_baton[Svn::Core::AUTH_PARAM_DEFAULT_PASSWORD] = config_password > > begin > ctx.checkout(config_repository_url, config_output_path, > config_revision.to_i, nil) > rescue Svn::Error::CLIENT_UNRELATED_RESOURCES => e # revision doesn't > exist > raise "no such revision " + revision.to_s + " at " + repos_uri > end >
Re: Subversion Ruby Binding: Server certificate verification failed: issuer is not trusted
Daniel Shahaf wrote on Thu, Apr 11, 2013 at 23:00:08 +0300: > Christian Plewnia wrote on Thu, Apr 11, 2013 at 20:51:26 +0200: > > Hi, > > > > I have been trying for some hours to use the ruby subversion binding to > > do a repository checkout. Unfortunately, the server certificate is not > > accepted: > > > > $ /.../script.rb > > /usr/lib/ruby/site_ruby/1.9.1/svn/util.rb:99:in `svn_client_checkout3': > > (Svn::Error::RaDavRequestFailed) > > Svn::Error::RaDavRequestFailed: OPTIONS of 'https://...': Server > > certificate verification failed: issuer is not trusted (https://...) > > from /usr/lib/ruby/site_ruby/1.9.1/svn/util.rb:99:in `checkout3' > > from /usr/lib/ruby/site_ruby/1.9.1/svn/client.rb:143:in `checkout' > > from /.../script.rb:22:in `' > > > > Using the SVN client from command line I never faced any certificate > > issues (as far as I know the certificate is perfectly valid). However, I > > started looking for a way to make the ruby script accept the > > certificate. As to my knowledge there is no documentation for the ruby > > binding, so I looked into the ruby files of the ruby binding and into > > the documentation of the C binding but I could not find a solution. > > > > Look at svn_cmdline_create_auth_baton(). You need to pass > trust_server_cert=TRUE (in C terms) or implement a prompt provider that > answers affirmatively. > > (or reconfigure your SSL library to trust that certificate by default, > in a level below Subversion) > > > The script (see below) is taken from the best piece of documentation I > > could find in the web: > > > > http://www.markdeepwell.com/2010/06/ruby-subversion-bindings/ ... > > ctx = Svn::Client::Context.new() > > ctx.add_simple_provider > > ctx.auth_baton[Svn::Core::AUTH_PARAM_DEFAULT_USERNAME] = config_username > > ctx.auth_baton[Svn::Core::AUTH_PARAM_DEFAULT_PASSWORD] = config_password > > I haven't seen this script in your previous example. The issue here is that the "simple provider" only answers username/password prompts; you need to a separate provider that answers SSL server certificate prompts. > > begin > > ctx.checkout(config_repository_url, config_output_path, > > config_revision.to_i, nil) > > rescue Svn::Error::CLIENT_UNRELATED_RESOURCES => e # revision doesn't > > exist > > raise "no such revision " + revision.to_s + " at " + repos_uri > > end > >
Re: feature suggestion: add elements of repo browser to log window
Ah, I'm sure you're right. Thanks! --- On Thu, 4/11/13, C. Michael Pilato wrote: From: C. Michael Pilato Subject: Re: feature suggestion: add elements of repo browser to log window To: "Don Stock" Cc: users@subversion.apache.org Date: Thursday, April 11, 2013, 2:45 PM On 04/11/2013 01:29 PM, Don Stock wrote: > I suggest adding the repo browser URL dropdown and tree to the log window, > where to save real estate it could for example show the tree in the URL > dropdown or have a Show Tree button. > > I initially didn't understand why certain versions were missing from the log > and tried to solve it while staying on the log window. If there had been a > dropdown or button there I surely would have looked at it. I'm guessing you've contacted the wrong mailing list. This list (users@subversion.apache.org) is for users of the Subversion core distribution, which includes command-line utilities only (nothing GUI-like). As such, we don't have "dropdowns", "windows", etc. Perhaps you meant to contact the us...@tortoisesvn.tigris.org list instead? -- C. Michael Pilato CollabNet <> www.collab.net <> Enterprise Cloud Development
