OSGeo maintains a set of subversion services, currently hosted on the primary Peer1 server at the virtual host http://svn.osgeo.org/. Subversion access is authenticated based on OSGeo Userids and each project has a committer list also maintained in LDAP. Excellent general information on subversion is available from the Subversion Book.
- http://svn.osgeo.org/fdo - FDO (also a bunch of old repositories exist for FDO)
- http://svn.osgeo.org/gdal - GDAL
- http://svn.osgeo.org/grass - GRASS GIS
- http://svn.osgeo.org/mapbender - Mapbender
- http://svn.osgeo.org/mapguide - MapGuide
- http://svn.osgeo.org/moss4g - MOSS4g
- http://svn.osgeo.org/osgeo - OSGeo
- http://svn.osgeo.org/ossim - OSSIM
- http://svn.osgeo.org/geos - GEOS
- http://svn.osgeo.org/mapserver - MapServer
- http://svn.osgeo.org/qgis - QGIS
- http://svn.osgeo.org/fusion - Fusion
- http://svn.osgeo.org/osgeo4w - OSGeo4W
Howard Butler (hobu), and Shawn Barnes (sbarnes) are the primary contacts for Subversion administration issues. Requests can be submitted via the SAC Trac.
Any member of a subversion committer group and add and remove members to the commiter group at an url of the following form, with the project name substituted for gdal. OSGeo Userids has details on finding or creating OSGeo userids.
Creating a repository
Create the repository on the main server:
$ sudo mkdir /var/www/svn/repos/<repo_name> $ sudo svnadmin create /var/www/svn/repos/<repo_name> $ sudo chown -R apache:apache /var/www/svn/repos/<repo_name>
Enable it's use from apache:
$ cd /etc/httpd/conf.d/subversion $ sudo cp osgeo4w.conf <repo_name>.conf $ sudo vi <repo_name>.conf (change all "osgeo4w' to "<repo_name>") $ sudo svn add <repo_name>.conf $ sudo svn commit -m "new repository added by frankw" <repo_name>.conf
Create the authorization group for the svn repository at:
Under "ou=svn" add a new entry of type groupOfNames, and add one initial admin's osgeo userid there in this form:
Loading a repository from a dumpfile
By root on main server:
$ sudo svnadmin load /var/www/svn/repos/<repo_name> < /path/to/dumpfile $ sudo chown -R apache:apache /var/www/svn/repos/<repo_name>
Dumping a repository
By root on main server:
$ sudo svnadmin dump /var/www/svn/repos/<repo_name> > dumpfile
Recovering / unlocking repository
- subversion may lock if user ctl-c during checkout or checkout is interupted with an apache restart
- Need policy on who to contact and who can run 'svnadmin recover' as
priviledged access is needed (may need to stop/start apache to drop requests to repository before recover)
Subversion was upgraded to version 1.4.3 (30 Jan. 2007) to reduce the repository locking problem if ctl-c used to end a checkout.
If the repository locks the following command should be used to recover the repository:
$ sudo svnadmin --wait recover /var/www/svn/repos/<repo_name> $ sudo chown -R apache:apache /var/www/svn/repos/<repo_name>
In most cases this will work in the odd case that you are waiting a very long time for the command to run then apache may have to be restarted to drop anything accessing the repository and preventing the repository from being recovered
$ sudo /sbin/service httpd restart $ sudo svnadmin --wait recover /var/www/svn/repos/<repo_name> $ sudo chown -R apache:apache /var/www/svn/repos/<repo_name>
By default we use one LDAP "group" for an entire subversion repository. Everyone in that group has commit priveledges on the whole repository. However, some project desire to have subgroups. For instance a core commiter group with update on the trunk source tree, and a broader contributor group that has commit access in a subarea, such as /sandbox. We accomplish this using an "authz" file to hold the rules for the respository, and multiple LDAP groups.
A project wishing this will need to prepare an authz template file looking something like:
[groups] committers = @@gdal@@ sandbox = @@gdal_sandbox@@ [/] * = r @committers = rw [/sandbox] * = r @committers = rw @sandbox = rw
This file should be submitted to SAC via a Trac ticket for placement on the server, and for creation of any corresponding LDAP groups. Thereafter any successful update via https://www.osgeo.org/cgi-bin/auth/ldap_group.py?group=project will result in the authz being generated from the corresponding authz.tmpl.
The authz.tmpl files need to be named exactly authz.tmpl and place in the corresponding project repository directory, /var/www/svn/repos/gdal for instance. Make sure the file is owned by apache.apache.
The corresponding /etc/httpd/conf.d/subversion/project.conf file should look something like the following. Note the removal of <LimitExcept> stuff, and reference to any specific ldap group as well as the AuthzSVNAccessFile.
<Location /gdal> DAV svn SVNPath /var/www/svn/repos/gdal AuthzSVNAccessFile /var/www/svn/repos/gdal/authz AuthType Basic AuthName "GDAL Subversion Repository" AuthLDAPURL ldap://18.104.22.168:389/ou=people,dc=osgeo,dc=org?uid?sub?(objectClass=*) Satisfy Any Require valid-user </Location>
The LDAP groups should be created as groupOfNames nodes below the ou=svn element using PHPLDAPAdmin. Make sure the membership is pre-initialized with an administrator for the project so they can do future updates themselves. Try to keep the names of the groups clearly related to the base project. eg. gdal, gdal_sandbox, gdal_documentors.
The script /root/scripts/ldap_update_authz.py script is run by an os.system() call out of ldap_group.py on any successful group update. It will scan for /var/www/svn/repos/*/authz.tmpl.
There are lots of things that can go wrong in the script which has poor error checking, and it might only manifest as some or all of the authz file no longer getting regenerated. So when an authz.tmpl file is put in place, or updated do a test update and verify that all authz files are being updated (check timestamps).
Anyone (on osgeo1) can run ldap_update_authz.py, but if authz files are created by someone that apache.apache can't delete, problems may ensue...