Hello,
As I read the SVN LTS policy, it states that support ends 4 years
after the initial release. Since Subversion 1.9 was released on Aug 5,
2015, does that now mean subversion 1.9 will not longer receive
security patches (now that it is Aug 6th)?
Thank you,
Ed
Hello,
I am configured as below:
Apache/2.4.39 (Unix) OpenSSL/1.0.2r SVN/1.12.0 mod_auth_gssapi/1.6.1
mod_dav_svn configured
Apache+SVN comes up clean, no errors.
I pointed the httpd.conf repo locations and access control files to
the legacy 1.8 repo's and get varying results. Some of the repo'
Does anyone have an idea how to fixthis error:
./configure --with-sqlite=/u01/tomcat/scm/sqlite-autoconf
--with-apxs=/u01/tomcat/scm/apache2.4.39kerb/bin/apxs
--prefix=/u01/tomcat/scm/subversion --enable-javah
l --with-jdk=/u01/weblogic/java/jdk1.8.0_201
--with-zlib=/u01/tomcat/scm/zlib-1.2.11
--
d
-- resuming normal operations
[Fri Dec 18 13:57:33.759296 2015] [mpm_prefork:info] [pid 44292] AH00164:
Server built: Dec 17 2015 14:22:22
On Fri, Dec 18, 2015 at 12:15 PM, Philip Martin
wrote:
> ken edward writes:
>
> > I installed
> > Subversion 1.8.14
> > Apache 2
Hello,
Please help...
I am able to use IE 11 to browse by apache+SVN+kerberos repo. Kerberos
works fine. No login required. However when I try to use Chrome or TSVN to
browse the repo, I can only get the content of the root repo (
https://myserver.com/cm_repo1). If I try to drill down into the pr