Comments on How To Install SVN With Apache dav_svn On CentOS 7

How To Install SVN With Apache dav_svn On CentOS 7 Apache Subversion, which is commonly referred to in its abbreviated form as SVN, (named after the command name SVN) is a popular software versioning and revision control system which is distributed as a free software under the Apache License. Outlined below are the steps in the process of installing and using of SVN and mod_dav_svn on CentOS 7

18 Comment(s)

Add comment

Please register in our forum first to comment.

Comments

By: taplinb

Great post! The examples executed flawlessly and got me started. -Brad

By: Jonesy

Unless I uncommented the "Alias /svn ..." line in 10-subversion.conf, TortoiseSVN would fail on checkout due to a "redirect cycle" error.  The repositories worked fine via a browser so it may have been something else in my distro's apache config but just FYI.  Might save someone else an hour of head bashing...

By: user01

you really did help me thanks a lot. but I saw ur comment after my head bashing :D

By: Simon

Good spot. Already spent an hour or two trying to figure that out, but I guess I would have spent one or two more.

By: Quin

Great post! I'm having one problem though--my repository won't come up on my browser. It just says the webpage is unavailable--it won't even ask for my username/password. It appears to be working in Putty (that's the ssh console I'm using), as my log appears when I put in the last command, but for some reason it won't work on my browser. Any help would be much appreciated. Thanks so much!

P.S. Just FYI I am using Centos 7, Putty, and Windows 8. I tried both Google Chrome and IE for browsers; neither worked.

By: Rajesh

Hi Quin, did you make it work? I am having the same problem..any ideas ?

By: Smail HSSIN

  Hello, Thank you very warmly!   Smail HSSIN

By: Tarun Maji]

Respected Sir,

Please help me sir now i am install svn server in centos 7, working fine, but one problem is that did not indexing example index.php, example, http://192.168.1.200/wordpress/php then see file extension please help me hot execute index.php file

By: Manish

All steps mentioned above were succesfull but I was not able to commit files.

I resolved this by changing permissions of all file in /var/www/svn/repo folder

cd /var/www/svn/repo

chown -R apache.apache .

By: Diego Padilla

Nice post

By: Vignesh

Hello sir, Thanks.Ur tutorial is awesome, but can u pls add how to access the svn with LDAP users,.(Means needs to be integrate svn with LDAP) Thanks

By: Javier Alvarado

This post is, by far, one of the best. It really helped me out. I have just one problem, when I try to commit, i got this error:  The server send an unknown return value:  (500 Internal Server Error) in response to the requeriment POST for '/svn/repo/!svn/me'. Do you have any idea? Thank you in advance

By: till

Take a look at the apache error.log, the reason for the 500 error should be listed there.

By: sans

Thanks for this awesome tutorial, I setup my SVN in 20 min flat!!

One question though - in my case, I have 2 projects and 2 separate teams for each project. I would like to prevent one team from accessing code of another team. How can I set this up?

 

Thanks

By: aigo

Almost!

svn: E000013: Can't open file '/var/www/svn/repo/db/txn-current-lock': Permission denied

How so?

By: aigo

Cloning repo directly results in this,

Redirecting to URL 'http://localhost/svn/repo':svn: E195019: Redirect cycle detected for URL 'http://localhost/svn/repo'

CentOS 7

-lg

By: aigo

Ok, set /var/www/svn/repo/db-logs.lock to 777 (as this seemed the only way to overcome that lock permission error), the next 777 permission to /var/www/svn/repo/db directory (as write only did not seem to be enough - what the heck!). Next is the warning at commit,

Warning: post commit FS processing had error:sqlite: attempt to write a readonly database

It still commits though, so for now I simply ignored it. Next is the hooks, I merely renamed the pre-commit.tmpl to pre-commit;

svn: E165001: Commit blocked by pre-commit hook (exit code 255) with no output.

Gave ex permission to it, commented all lines out, the hook does absolutely nothing, still blocks the commit.

So it is either svn setup problem (doubtful), or the CentOS (7) is gradually submerging into the GarbageOS, or the svn is no longer to be used as the serious version control system in this combination. In fact if the "svnadmin create repo .." did indeed create repo with the wrong permissions in it, then we do have a problem.

Any thoughts?

 

 

By: aigo

Ah, disabled SELinux, that did it! What a garbage!

Thanks for the article!

-lg