Hello
Thanks so much for providing the subversion modules - we're using mod_svn-1.8.13-ap24-x64.zip very successfully and it is so easy to install.
Is there any plan to upgrade the Subversion builds, as 1.9.0 is now out ? We'd be happy to test and report back if that would help...
Many Thanks in advance..
Simon
There is a plan to build it. I already made a build how to based on the beta releases. https://gist.github.com/JBlond/d626693182dbfa5994f1
I only did not had the time to do so.
+1 on the packages, thank you so very much! Add my vote for SVN 1.9 - when you get around to it - we're in the middle of a new server build out (upgrading from 1.6) and would love to be on the latest.
if you do the upgrade you have to do a dump and import the dump. Do not use the old repo. It might works, but I had heavy problems with that after some time.
Was definitely planning on doing so - thanks for the tip :)
I made a bit progess building 1.9.0, but I have an issue with the new serf version. I was never lucky with the 1.3.x version of it. So I used 1.2.1 for the older builds, but the current readme says that it needs at least 1.3.4
Thanks for the update, Mario. Wish I could be of more assistance.
I figured out today that I need scons ( a tool for python) to build serf for svn. I think until late Sunday ( CEST) I can do the build and some tests.
Thanks Mario. Any luck?
I did the build. All stuff built except of one required apache module and there are only three. I look into that tonight / night.
After that I do some stress testing and then I'll upload binaries.
I hope that it won't take long.
Yesterday wasn't much time cause my granny celebrated her 87th birthday ^__^ That seemed to be a better option instead of debugging a build.
Totally agree on the bday being more important!! Thanks again for the update!
it is done. The dll's are still glowing from the CPU heat. Grab your copy as long it is fresh.
Awesome, nicely done Mario!! I will crack it open and give it a run-through today/tomorrow - and report back. Thanks!!
Hello. Best birthday wishes to your Gran - 87 is well worth a party ;D ;D
I have installed and am running the 1.90 subversion. I replaced a fully operational 1.8.13 (test) environment. All seemed to work well at first, have re-imported a repository from a data dump, can browse to it using URL, can do anything readonly, but when I try and commit anything I get an authentication error. Also when I try and sync with my main production subversion (still at 1.7.8) I get this :
svnsync init --allow-non-empty <target repo URL> <source rep URL>
svnsync: E120190: Error running context: An error occurred during authentication
All of this worked fine with Subversion 1.8.13 modules.
I will probably switch back to 1.8.13 for now but I can fire up my 1.90 env if needed for debugging/testing. Any suggestions on how to find out what it is ?
Thanks
Which Apache version do you use? I know that some older 2.4.x version have issues with the auth due an auth bug.
#if AP_MODULE_MAGIC_AT_LEAST(20060110,0) /* version where
ap_some_auth_required breaks */
# if AP_MODULE_MAGIC_AT_LEAST(20120211,47) /* first version with
force_authn hook and
ap_some_authn_required() which
allows us to work without
ap_some_auth_required() */
# define USE_FORCE_AUTHN 1
# define IN_SOME_AUTHN_NOTE "authz_svn-in-some-authn"
# define FORCE_AUTHN_NOTE "authz_svn-force-authn"
# else
/* ap_some_auth_required() is busted and no viable alternative exists */
# ifndef SVN_ALLOW_BROKEN_HTTPD_AUTH
# error This version of httpd has a security hole with mod_authz_svn
# else
/* user wants to build anyway */
# define USE_FORCE_AUTHN 0
# endif
# endif
#else
/* old enough that ap_some_auth_required() still works */
# define USE_FORCE_AUTHN 0
#endif
So you need at least 2.4.13
My apache setup is as follows :
2.4.16 x64
mod_auth_ntlm 1.0.24x
openssl 1.01p
Quote from: SimonR on September 02, 2015, 10:43:57 AM
but I can fire up my 1.90 env if needed for debugging/testing. Any suggestions on how to find out what it is ?
in the test env you can set the log level to debug and see in the logs what is happening.
The only difference I see to my testing was that I compiled snv against OpenSSL 1.0.2 So there might be a problem if the client can't connect. But that is only a guessing. But insce you use the command line that shouldn't be an issue.
since Today there is 1.9.1 you can take a look into http://svn.apache.org/repos/asf/subversion/tags/1.9.1/CHANGES
Did you use --username syncuser --password XXXXXXX for svnsync ?
I did try with a defined user and password, no change
I also tried setting the Apache LogLevel to Debug on both source and target (Source is live server, target is test mirror server) and there was no log activity in either when the call failed.
Also emphasise that the command that doesn't work on 1.9.0 worked fine on 1.8.13 pointing at the same live server (which is still on 1.7.8 until we upgrade soon)
So
1.7.8 <> 1.8.13 svnsync init command works
1.7.8 <> 1.9.0 svnsync init fails
What I did not was creating a new empty repo and synced the old one into the new repo
C:\Users\mario\Apache24\bin>svnsync sync --username mario --password FANCYPASSWORD https://srv8/test_repo https://srv7/orig
Hmmm ok maybe it's something in the NTLM i am using, which works with 1.8.13. I'll try disabling that and see if I can get it to play ball. Thanks for your help.
My authentication settings needed adjusting. All working now, loading repository from dump, initialising sync and updating mirror all working. Commits also working now. :-) :)
However to do that I have to have '* = rw' in my AuthzSVNAccessFile
If I attempt to have '* = r' and specific named users or groups as 'rw', it doesn't allow you to write to the repository :( :(.
It did in SVN 1.8.13
The permisison thing seems to be a bit different in 1.9 ( I haven used it in a long time) than I remember it. Take a look at https://svn.apache.org/repos/asf/subversion/branches/1.9.x/subversion/mod_authz_svn/INSTALL
if that doesn't help there is also mod_dontdothat ( don't do that). https://svn.apache.org/repos/asf/subversion/branches/1.9.x/tools/server-side/mod_dontdothat/README
That is also in the apache haus release.
Just as an update: I'm working on 1.9.1
Thanks for the pointers - I will take a look. ;D
Working here as well with latest Apache and SVN. THanks Mario!
Would it be possible to get mod_svn 1.9.2 x64 for Apache 2.4.x in vc9 ?
The VC11 modules do load in VC9. I won't build VC9 anymore. it was too hard to keep two operating systems up to date to have two different compiler / VC versions.
Can't you update to VC11 version of apache?
i understand. i'll give the vc11 mod svn module a try. i'm limited to vc9 as mod_wsgi uses python 2.7
If that doesn't work out we / I may try to compile mod_wsgi with VC 11. Please let us know if that worked.
VC9 is not EOL, not till 4/2018 (https://support.microsoft.com/en-us/lifecycle/search?sort=PN&alpha=Visual%20Studio). Just saying :)
No luck with the vc11 mod_svn in my environment. If you do build mod_wsgi for vc11 for apache 2.4 64 bit that would be awesome.
Try these ones:
https://phpdev.toolsforresearch.com/svn_vc9_x86.zip
https://phpdev.toolsforresearch.com/svn_vc9_x64.zip