From ArchWiki


It also works with Eclipse and Subclipse! Make sure to use https://localhost/svn/test ! The inital import is done with the shell like in the wiki described. Then go to Eclipse, add the SVN Rep and checkout as project!

How to delete a repo?

Anybody knows how to delete a svn repo?. It would be useful to say that in our wiki page too. Thanks

Sorry for the excessive amounts of revisions; having all of the references to cactus is annoying, although he was awesome for making this wiki page in the first place. --Jordoex 03:24, 8 March 2009 (EDT)

Subversion without a server

If you search for "subversion", the wiki automatically redirects here but there's no indication that it is possible to use it without running either sort of server. One reason to do this is to keep e.g. research papers under version control, just accessing the repository via the filesystem. (This can be integrated with laTeX, for example.) --Margali 21:43, 22 December 2011 (EST)

Well, the title just says "Subversion Setup", you are free to add a section for setting up a local repo too :) You may also want to restructure the article a bit to have e.g. a more generic introduction, just pay attention not to lose relevant content and to split your changes in as many logical edits as possible, always writing some explanation words in the Summary field. -- Kynikos 07:44, 24 December 2011 (EST)

Some revisions

several things that arent clear right off the bat.

"Apache for Subversion setup" is if you want to have file access the svn repository via http, where as "Svnserve" is a much simpler setup to access via local machine, or SSH

In the "Apache for subversion setup" wiki, If your not going to use SSL you still need add the <Location> directive. In this case you can put the directive in /etc/httpd/conf/extra/httpd-dav.conf, or you can put it in httpd-vhosts.conf. Personally i think the most logical place for svn directives is in the httpd-dav.conf since svn is dav related.

The term "Project", in the wiki, is the collection of files that your working on that you want versioned.

The terms "USER_NAME" and "REPO_NAME" are variables that need to filled in by you. (you might want to name your REPO_NAME the same name as your project folder)

A nice SVN help file --Wolfdogg 04:59, 22 January 2012 (EST)

Error message help

If when you run 'svn commit' and get an error

  svn: E205007: Commit failed (details follow):
  svn: E205007: Could not use external editor to fetch log message; consider setting the $SVN_EDITOR environment variable or using the --message (-m) or --file (-F) options
  svn: E205007: None of the environment variables SVN_EDITOR, VISUAL or EDITOR are set, and no 'editor-cmd' run-time configuration option was found

you will either need to run your commit commands with the -m option with a comment next time around and always, you can use the --editor option, or you can add the environment var

  $ SVN_EDITOR=nano 
  $ export SVN_EDITOR

If you get the error

  Can't open file '/path/to/repos/db/txn-current-lock': Permission denied

You need to check the file permissions and re chown them --Wolfdogg 22:19, 22 January 2012 (EST)

Ideas that still need thought out

Assume the development machine isnt always a linux. i guess its safe to assume the server is, since the wiki is being followed as an arch wiki.

For the following commands;

   chown -R http.http /home/svn/repositories/REPO_NAME
   cp -R /home/USER_NAME/project/REPO_NAME/code/* trunk

assume the reponame was "repo1" but the project is actually the name of the website such as website-com The term REPO_NAME is no longer a valid variable to use in both. maybe we shoudl use REPO_NAME, and PROJECT_NAME? Or we shoudl make it clear to name the REPO_NAME the same as the project name.

Out of curiosity, what else would ever reside in the /svn directory besides repositories? So why use the extra directory of /svn/repositories/REPO_NAME, why not just /svn/REPO_NAME? I know its all common usage, but is there a real valid reason for this?