Hi Team,
We have recently upgraded subversion 1.6 to 1.7. During the sniff testing we
found without "HTTPV3 protocol Off " commit functionality is not working?
Please help us to fix this issue.
We have investigated the issue and tested couple of scenarios to validate it.
1. Disabled Ldap/per
On Jun 20, 2012, at 00:01, dhanushka ranasinghe wrote:
> i have svn repo that can be checkout from both http and https, but commits
> are only allowed via https. issue is when we checking out svn form http ...
> i get following waring ...
>
> is there any reason for that
>
> Fetching extern
Hi guys ,
i have svn repo that can be checkout from both http and https, but commits
are only allowed via https. issue is when we checking out svn form http
... i get following waring ...
is there any reason for that
Fetching external item into 'modules/'
svn: warning: '*http*://svn.khc.com/rep
Building Subversion 1.7.5 on Solaris 8 with the vendor (SunPRO) compiler
fails with errors of the form
"subversion/libsvn_subr/sqlite.c", line 1208: non-constant initializer: op
"NAME"
cc: acomp failed for subversion/libsvn_subr/sqlite.c
gmake: *** [subversion/libsvn_subr/sqlite.lo] E
host:/tmp/subversion$ ./get-deps.sh
[script output elided]
host:/tmp/subversion$ find . -name apr_hash.c
./apr/tables/apr_hash.c
host:/tmp/subversion$ ./get-deps.sh
[script output elided]
host:/tmp/subversion$ find . -name apr_hash.c
./apr/apr-1.4.6/tables/apr_hash.c
./apr/tables/apr_hash.c
Re
The apr-util package accepts an option --with-expat, described in the
configure script help output as
--with-expat=DIRspecify Expat location, or 'builtin'
I want to use 'builtin'. Knowing that the options I give to Subversion's
top-level configure script are passed down to the sub-pro
On Thu, May 03, 2012 at 01:13:30PM +0200, Stefan Sperling wrote:
> Hello users@,
>
> elego is presenting a small Subversion conference in June this year.
>
> The conference targets professional Subversion users and features
> workshops and talks about Subversion. This is a chance of getting
> to
>
> Are you sure you've set the ownership *and* permissions *and* SELinux
> security context correctly for /var/www/svn *and* all of its contents
> recursively?
>
>
>
Hey even after I owned the whole svn folder by apache again and gave every
user read,write and execute rights it was not working.
Wh
