JavaHL: "Not implemented" error in StatusEditor.addAbsent
Hi I just wanted to report that we are affected by this bug and would be grateful if the developers will include Marc Strapetz's patch (submitted on developers mailing list on 11 Dec) in the next Subversion release. Best regards David
Regarding install and running svn1.9.2 for svnserve and http access in browser
Hi Team, I have situation which needs your suggestion and help in setting up the svn1.9.2 with svnserve + http access in browser. My below talks about my svn setup. *SVN working method:* After installation, the svn://servername/reponame is working. But http://servername/reponame is not working and give the HTTP 404 error. *Problem Description:* Am i missing something. I know Svn Apache modules are required for http access but i am running svnserve for client access and no Apache httpd is installed. For http access i have installed Serf library. *Expected : * - What are required for running svn1.9.2 as svnserve daemon (with http support in browser) -Is just serf library is not enough to serve http through svnserve -how to pass the httpd modules to during subversion install Please suggest how to proceed in this situation. I have already installed the svn without serf in production and now would like to configure svn with http support in the custom path. Thank you. *ENV Description* *Redhat Linux* - Redhat 7 *SVN install type* - Install from Source/TAR ball *Install to Custom path* - Like /local/application/packages/svn1.9.2 *TAR ball path* - /local/application/source/subversion-1.9.2 *SVN access method(as daemon)* - /local/application/packages/svn1.9.2/bin/svnserve -d -r *Pre-requisite installed location* - to custom path like svn *Pre-requisite installed* are - apr-1.5.2, apr-util-1.5.4, serf-1.3.8,scons-2.4.1,Python-2.7.11,openssl-1.0.2e [ all source/tar install from source to custom path] *Path set* - /local/application/pacakges/source/scons/script to PATH variable. I have set the scons custom install path but svn configure script is not taking the libserf-1.so. so set the serf source path to script folder in PATH variable and it takes the serf. *svn1.9.2 install options* ./configure --prefix=/local/application/packages/svn-1.9.2 --with-serf=/local/application/packages/serf1.3.8 --with-apr=/local/application/packages/apr-config-1 --with-apr-util=/local/application/packages/apr-config-1 --disable-static --with-sqlite=/local/application/pacakges/source/subversion-1.9.2/sqlite-amalgamation-3081101/sqlite3.c make make install regards, Arun
Re: Regarding install and running svn1.9.2 for svnserve and http access in browser
On Dec 17, 2015, at 8:09 AM, arun prasath wrote: > I have situation which needs your suggestion and help in setting up the > svn1.9.2 with svnserve + http access in browser. My below talks about my svn > setup. > SVN working method: > After installation, the svn://servername/reponame is working. But > http://servername/reponame is not working and give the HTTP 404 error. > > Problem Description: > Am i missing something. I know Svn Apache modules are required for http > access but i am running svnserve for client access and no Apache httpd is > installed. For http access i have installed Serf library. > > Expected : > - What are required for running svn1.9.2 as svnserve daemon (with http > support in browser) > -Is just serf library is not enough to serve http through svnserve > -how to pass the httpd modules to during subversion install Apache + mod_dav_svn is required to serve a Subversion repository over http (or https). You can run this simultaneously with svnserve for serving the repository over the svn protocol, provided you set up permissions/ownership properly. There's documentation in the book. However, I'm not sure what benefit there is to offering multiple access methods. For example, if you want to serve the repository over http via Apache + mod_dav_svn, then why also run svnserve? serf is the library the svn client uses to access a repository that is being served by Apache + mod_dav_svn.
svn + SSL?
Has there been any thought to added SSL/TLS to the svn protocol? Setting up Apache for https is a bit heavy and SSH requires the existence of local users. Adding TLS doesn't seem like it would be that hard and would help when using SASL/LDAP when passing plaintext passwords.
Re: Regarding install and running svn1.9.2 for svnserve and http access in browser
Hi Ryan, Thanks for the info. I am running svnserve for client access through TortoiseSVN. This is for users who wants to checkout and checkin the code. There are some users who just want to browse the code in Internet Explorer. The http in browser is required for users who browse code without checkout using TortoiseSVN client. How to achieve this. So, I have installed svn using configure.sh script i have used the serf library path. But serf is not serving the http for svn repository. So my doubt is whether the following option will provide http support when svn is installed with below options. I hope this explains what my requirement is. --with-apxs[=FILE] Build shared Apache modules. FILE is the optional pathname to the Apache apxs tool; defaults to "apxs". --with-apache-libexecdir[=PATH] Install Apache modules to Apache's configured modules directory instead of LIBEXECDIR; if PATH is given, install to PATH. regards, Arun On Fri, Dec 18, 2015 at 12:04 AM, Ryan Schmidt < subversion-2...@ryandesign.com> wrote: > > On Dec 17, 2015, at 8:09 AM, arun prasath wrote: > > > I have situation which needs your suggestion and help in setting up the > svn1.9.2 with svnserve + http access in browser. My below talks about my > svn setup. > > SVN working method: > > After installation, the svn://servername/reponame is working. But > http://servername/reponame is not working and give the HTTP 404 error. > > > > Problem Description: > > Am i missing something. I know Svn Apache modules are required for http > access but i am running svnserve for client access and no Apache httpd is > installed. For http access i have installed Serf library. > > > > Expected : > > - What are required for running svn1.9.2 as svnserve daemon (with http > support in browser) > > -Is just serf library is not enough to serve http through svnserve > > -how to pass the httpd modules to during subversion install > > Apache + mod_dav_svn is required to serve a Subversion repository over > http (or https). You can run this simultaneously with svnserve for serving > the repository over the svn protocol, provided you set up > permissions/ownership properly. There's documentation in the book. However, > I'm not sure what benefit there is to offering multiple access methods. For > example, if you want to serve the repository over http via Apache + > mod_dav_svn, then why also run svnserve? > > serf is the library the svn client uses to access a repository that is > being served by Apache + mod_dav_svn. > > >
Re: Regarding install and running svn1.9.2 for svnserve and http access in browser
Guten Tag arun prasath, am Freitag, 18. Dezember 2015 um 08:33 schrieben Sie: > I am running svnserve for client access through TortoiseSVN. This > is for users who wants to checkout and checkin the code. TortoiseSVN can handle checkouts and such over HTTP as well, there's no need to use svnserve for that reason. > There are some users who just want to browse the code in Internet > Explorer. The http in browser is required for users who browse code > without checkout using TortoiseSVN client. How to achieve this. Ryan already gave the necessary keywords: http://svnbook.red-bean.com/en/1.8/svn.serverconfig.httpd.html > So, I have installed svn using configure.sh script[...] From my opinion you should prefer the packages provided by your distribution. > But serf is not serving the http for svn repository. Because that is the purpose of httpd and mod_dav_svn, serf is client side. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...05151- 9468- 55 Fax...05151- 9468- 88 Mobil..0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
