| 1 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/events/actions/repository-modify mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/events/actions/repository-modify |
| 2 |
--- smeserver-subversion-1.2/root/etc/e-smith/events/actions/repository-modify 2006-08-26 23:59:54.000000000 +0200 |
| 3 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/events/actions/repository-modify 2007-08-06 20:55:35.000000000 +0200 |
| 4 |
@@ -53,7 +53,7 @@ |
| 5 |
# Create the repository files |
| 6 |
#------------------------------------------------------------ |
| 7 |
|
| 8 |
- system("/bin/cp", "-Rp", "/etc/e-smith/skel/repository", |
| 9 |
+ system("/usr/bin/svnadmin", "create", |
| 10 |
"/home/e-smith/files/repositories/$repositoryName") == 0 |
| 11 |
or die "Error copying repository skeletal files"; |
| 12 |
|
| 13 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/conf/authz mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/conf/authz |
| 14 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/conf/authz 2006-08-26 23:59:56.000000000 +0200 |
| 15 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/conf/authz 1970-01-01 01:00:00.000000000 +0100 |
| 16 |
@@ -1,21 +0,0 @@ |
| 17 |
-### This file is an example authorization file for svnserve. |
| 18 |
-### Its format is identical to that of mod_authz_svn authorization |
| 19 |
-### files. |
| 20 |
-### As shown below each section defines authorizations for the path and |
| 21 |
-### (optional) repository specified by the section name. |
| 22 |
-### The authorizations follow. An authorization line can refer to a |
| 23 |
-### single user, to a group of users defined in a special [groups] |
| 24 |
-### section, or to anyone using the '*' wildcard. Each definition can |
| 25 |
-### grant read ('r') access, read-write ('rw') access, or no access |
| 26 |
-### (''). |
| 27 |
- |
| 28 |
-# [groups] |
| 29 |
-# harry_and_sally = harry,sally |
| 30 |
- |
| 31 |
-# [/foo/bar] |
| 32 |
-# harry = rw |
| 33 |
-# * = |
| 34 |
- |
| 35 |
-# [repository:/baz/fuz] |
| 36 |
-# @harry_and_sally = rw |
| 37 |
-# * = r |
| 38 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/conf/passwd mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/conf/passwd |
| 39 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/conf/passwd 2006-08-26 23:59:56.000000000 +0200 |
| 40 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/conf/passwd 1970-01-01 01:00:00.000000000 +0100 |
| 41 |
@@ -1,8 +0,0 @@ |
| 42 |
-### This file is an example password file for svnserve. |
| 43 |
-### Its format is similar to that of svnserve.conf. As shown in the |
| 44 |
-### example below it contains one section labelled [users]. |
| 45 |
-### The name and password for each user follow, one account per line. |
| 46 |
- |
| 47 |
-# [users] |
| 48 |
-# harry = harryssecret |
| 49 |
-# sally = sallyssecret |
| 50 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/conf/svnserve.conf mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/conf/svnserve.conf |
| 51 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/conf/svnserve.conf 2006-08-26 23:59:56.000000000 +0200 |
| 52 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/conf/svnserve.conf 1970-01-01 01:00:00.000000000 +0100 |
| 53 |
@@ -1,30 +0,0 @@ |
| 54 |
-### This file controls the configuration of the svnserve daemon, if you |
| 55 |
-### use it to allow access to this repository. (If you only allow |
| 56 |
-### access through http: and/or file: URLs, then this file is |
| 57 |
-### irrelevant.) |
| 58 |
- |
| 59 |
-### Visit http://subversion.tigris.org/ for more information. |
| 60 |
- |
| 61 |
-# [general] |
| 62 |
-### These options control access to the repository for unauthenticated |
| 63 |
-### and authenticated users. Valid values are "write", "read", |
| 64 |
-### and "none". The sample settings below are the defaults. |
| 65 |
-# anon-access = read |
| 66 |
-# auth-access = write |
| 67 |
-### The password-db option controls the location of the password |
| 68 |
-### database file. Unless you specify a path starting with a /, |
| 69 |
-### the file's location is relative to the conf directory. |
| 70 |
-### Uncomment the line below to use the default password file. |
| 71 |
-# password-db = passwd |
| 72 |
-### The authz-db option controls the location of the authorization |
| 73 |
-### rules for path-based access control. Unless you specify a path |
| 74 |
-### starting with a /, the file's location is relative to the conf |
| 75 |
-### directory. If you don't specify an authz-db, no path-based access |
| 76 |
-### control is done. |
| 77 |
-### Uncomment the line below to use the default authorization file. |
| 78 |
-# authz-db = authz |
| 79 |
-### This option specifies the authentication realm of the repository. |
| 80 |
-### If two repositories have the same authentication realm, they should |
| 81 |
-### have the same password database, and vice versa. The default realm |
| 82 |
-### is repository's uuid. |
| 83 |
-# realm = My First Repository |
| 84 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/current mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/current |
| 85 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/current 2006-08-26 23:59:59.000000000 +0200 |
| 86 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/current 1970-01-01 01:00:00.000000000 +0100 |
| 87 |
@@ -1 +0,0 @@ |
| 88 |
-0 1 1 |
| 89 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/format mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/format |
| 90 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/format 2006-08-26 23:59:59.000000000 +0200 |
| 91 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/format 1970-01-01 01:00:00.000000000 +0100 |
| 92 |
@@ -1 +0,0 @@ |
| 93 |
-1 |
| 94 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/fs-type mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/fs-type |
| 95 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/fs-type 2006-08-26 23:59:59.000000000 +0200 |
| 96 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/fs-type 1970-01-01 01:00:00.000000000 +0100 |
| 97 |
@@ -1 +0,0 @@ |
| 98 |
-fsfs |
| 99 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/revprops/0 mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/revprops/0 |
| 100 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/revprops/0 2006-08-26 23:59:58.000000000 +0200 |
| 101 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/revprops/0 1970-01-01 01:00:00.000000000 +0100 |
| 102 |
@@ -1,5 +0,0 @@ |
| 103 |
-K 8 |
| 104 |
-svn:date |
| 105 |
-V 27 |
| 106 |
-2006-03-11T22:31:43.293432Z |
| 107 |
-END |
| 108 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/revs/0 mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/revs/0 |
| 109 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/revs/0 2006-08-26 23:59:58.000000000 +0200 |
| 110 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/revs/0 1970-01-01 01:00:00.000000000 +0100 |
| 111 |
@@ -1,11 +0,0 @@ |
| 112 |
-PLAIN |
| 113 |
-END |
| 114 |
-ENDREP |
| 115 |
-id: 0.0.r0/17 |
| 116 |
-type: dir |
| 117 |
-count: 0 |
| 118 |
-text: 0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e |
| 119 |
-cpath: / |
| 120 |
- |
| 121 |
- |
| 122 |
-17 107 |
| 123 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/uuid mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/uuid |
| 124 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/uuid 2006-08-26 23:59:59.000000000 +0200 |
| 125 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/db/uuid 1970-01-01 01:00:00.000000000 +0100 |
| 126 |
@@ -1 +0,0 @@ |
| 127 |
-88c78cac-bf0e-0410-adb0-b8c07132d217 |
| 128 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/format mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/format |
| 129 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/format 2006-08-26 23:59:59.000000000 +0200 |
| 130 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/format 1970-01-01 01:00:00.000000000 +0100 |
| 131 |
@@ -1 +0,0 @@ |
| 132 |
-3 |
| 133 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/post-commit.tmpl mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/post-commit.tmpl |
| 134 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/post-commit.tmpl 2006-08-26 23:59:56.000000000 +0200 |
| 135 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/post-commit.tmpl 1970-01-01 01:00:00.000000000 +0100 |
| 136 |
@@ -1,51 +0,0 @@ |
| 137 |
-#!/bin/sh |
| 138 |
- |
| 139 |
-# POST-COMMIT HOOK |
| 140 |
-# |
| 141 |
-# The post-commit hook is invoked after a commit. Subversion runs |
| 142 |
-# this hook by invoking a program (script, executable, binary, etc.) |
| 143 |
-# named 'post-commit' (for which this file is a template) with the |
| 144 |
-# following ordered arguments: |
| 145 |
-# |
| 146 |
-# [1] REPOS-PATH (the path to this repository) |
| 147 |
-# [2] REV (the number of the revision just committed) |
| 148 |
-# |
| 149 |
-# The default working directory for the invocation is undefined, so |
| 150 |
-# the program should set one explicitly if it cares. |
| 151 |
-# |
| 152 |
-# Because the commit has already completed and cannot be undone, |
| 153 |
-# the exit code of the hook program is ignored. The hook program |
| 154 |
-# can use the 'svnlook' utility to help it examine the |
| 155 |
-# newly-committed tree. |
| 156 |
-# |
| 157 |
-# On a Unix system, the normal procedure is to have 'post-commit' |
| 158 |
-# invoke other programs to do the real work, though it may do the |
| 159 |
-# work itself too. |
| 160 |
-# |
| 161 |
-# Note that 'post-commit' must be executable by the user(s) who will |
| 162 |
-# invoke it (typically the user httpd runs as), and that user must |
| 163 |
-# have filesystem-level permission to access the repository. |
| 164 |
-# |
| 165 |
-# On a Windows system, you should name the hook program |
| 166 |
-# 'post-commit.bat' or 'post-commit.exe', |
| 167 |
-# but the basic idea is the same. |
| 168 |
-# |
| 169 |
-# The hook program typically does not inherit the environment of |
| 170 |
-# its parent process. For example, a common problem is for the |
| 171 |
-# PATH environment variable to not be set to its usual value, so |
| 172 |
-# that subprograms fail to launch unless invoked via absolute path. |
| 173 |
-# If you're having unexpected problems with a hook program, the |
| 174 |
-# culprit may be unusual (or missing) environment variables. |
| 175 |
-# |
| 176 |
-# Here is an example hook script, for a Unix /bin/sh interpreter. |
| 177 |
-# For more examples and pre-written hooks, see those in |
| 178 |
-# the Subversion repository at |
| 179 |
-# http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and |
| 180 |
-# http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/ |
| 181 |
- |
| 182 |
- |
| 183 |
-REPOS="$1" |
| 184 |
-REV="$2" |
| 185 |
- |
| 186 |
-commit-email.pl "$REPOS" "$REV" commit-watchers@example.org |
| 187 |
-log-commit.py --repository "$REPOS" --revision "$REV" |
| 188 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/post-lock.tmpl mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/post-lock.tmpl |
| 189 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/post-lock.tmpl 2006-08-26 23:59:56.000000000 +0200 |
| 190 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/post-lock.tmpl 1970-01-01 01:00:00.000000000 +0100 |
| 191 |
@@ -1,44 +0,0 @@ |
| 192 |
-#!/bin/sh |
| 193 |
- |
| 194 |
-# POST-LOCK HOOK |
| 195 |
-# |
| 196 |
-# The post-lock hook is run after a path is locked. Subversion runs |
| 197 |
-# this hook by invoking a program (script, executable, binary, etc.) |
| 198 |
-# named 'post-lock' (for which this file is a template) with the |
| 199 |
-# following ordered arguments: |
| 200 |
-# |
| 201 |
-# [1] REPOS-PATH (the path to this repository) |
| 202 |
-# [2] USER (the user who created the lock) |
| 203 |
-# |
| 204 |
-# The paths that were just locked are passed to the hook via STDIN (as |
| 205 |
-# of Subversion 1.2, only one path is passed per invocation, but the |
| 206 |
-# plan is to pass all locked paths at once, so the hook program |
| 207 |
-# should be written accordingly). |
| 208 |
-# |
| 209 |
-# The default working directory for the invocation is undefined, so |
| 210 |
-# the program should set one explicitly if it cares. |
| 211 |
-# |
| 212 |
-# Because the lock has already been created and cannot be undone, |
| 213 |
-# the exit code of the hook program is ignored. The hook program |
| 214 |
-# can use the 'svnlook' utility to help it examine the |
| 215 |
-# newly-created lock. |
| 216 |
-# |
| 217 |
-# On a Unix system, the normal procedure is to have 'post-lock' |
| 218 |
-# invoke other programs to do the real work, though it may do the |
| 219 |
-# work itself too. |
| 220 |
-# |
| 221 |
-# Note that 'post-lock' must be executable by the user(s) who will |
| 222 |
-# invoke it (typically the user httpd runs as), and that user must |
| 223 |
-# have filesystem-level permission to access the repository. |
| 224 |
-# |
| 225 |
-# On a Windows system, you should name the hook program |
| 226 |
-# 'post-lock.bat' or 'post-lock.exe', |
| 227 |
-# but the basic idea is the same. |
| 228 |
-# |
| 229 |
-# Here is an example hook script, for a Unix /bin/sh interpreter: |
| 230 |
- |
| 231 |
-REPOS="$1" |
| 232 |
-USER="$2" |
| 233 |
- |
| 234 |
-# Send email to interested parties, let them know a lock was created: |
| 235 |
-mailer.py lock "$REPOS" "$USER" /path/to/mailer.conf |
| 236 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/post-revprop-change.tmpl mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/post-revprop-change.tmpl |
| 237 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/post-revprop-change.tmpl 2006-08-26 23:59:56.000000000 +0200 |
| 238 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/post-revprop-change.tmpl 1970-01-01 01:00:00.000000000 +0100 |
| 239 |
@@ -1,56 +0,0 @@ |
| 240 |
-#!/bin/sh |
| 241 |
- |
| 242 |
-# POST-REVPROP-CHANGE HOOK |
| 243 |
-# |
| 244 |
-# The post-revprop-change hook is invoked after a revision property |
| 245 |
-# has been added, modified or deleted. Subversion runs this hook by |
| 246 |
-# invoking a program (script, executable, binary, etc.) named |
| 247 |
-# 'post-revprop-change' (for which this file is a template), with the |
| 248 |
-# following ordered arguments: |
| 249 |
-# |
| 250 |
-# [1] REPOS-PATH (the path to this repository) |
| 251 |
-# [2] REV (the revision that was tweaked) |
| 252 |
-# [3] USER (the username of the person tweaking the property) |
| 253 |
-# [4] PROPNAME (the property that was changed) |
| 254 |
-# [5] ACTION (the property was 'A'dded, 'M'odified, or 'D'eleted) |
| 255 |
-# |
| 256 |
-# [STDIN] PROPVAL ** the old property value is passed via STDIN. |
| 257 |
-# |
| 258 |
-# Because the propchange has already completed and cannot be undone, |
| 259 |
-# the exit code of the hook program is ignored. The hook program |
| 260 |
-# can use the 'svnlook' utility to help it examine the |
| 261 |
-# new property value. |
| 262 |
-# |
| 263 |
-# On a Unix system, the normal procedure is to have 'post-revprop-change' |
| 264 |
-# invoke other programs to do the real work, though it may do the |
| 265 |
-# work itself too. |
| 266 |
-# |
| 267 |
-# Note that 'post-revprop-change' must be executable by the user(s) who will |
| 268 |
-# invoke it (typically the user httpd runs as), and that user must |
| 269 |
-# have filesystem-level permission to access the repository. |
| 270 |
-# |
| 271 |
-# On a Windows system, you should name the hook program |
| 272 |
-# 'post-revprop-change.bat' or 'post-revprop-change.exe', |
| 273 |
-# but the basic idea is the same. |
| 274 |
-# |
| 275 |
-# The hook program typically does not inherit the environment of |
| 276 |
-# its parent process. For example, a common problem is for the |
| 277 |
-# PATH environment variable to not be set to its usual value, so |
| 278 |
-# that subprograms fail to launch unless invoked via absolute path. |
| 279 |
-# If you're having unexpected problems with a hook program, the |
| 280 |
-# culprit may be unusual (or missing) environment variables. |
| 281 |
-# |
| 282 |
-# Here is an example hook script, for a Unix /bin/sh interpreter. |
| 283 |
-# For more examples and pre-written hooks, see those in |
| 284 |
-# the Subversion repository at |
| 285 |
-# http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and |
| 286 |
-# http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/ |
| 287 |
- |
| 288 |
- |
| 289 |
-REPOS="$1" |
| 290 |
-REV="$2" |
| 291 |
-USER="$3" |
| 292 |
-PROPNAME="$4" |
| 293 |
-ACTION="$5" |
| 294 |
- |
| 295 |
-propchange-email.pl "$REPOS" "$REV" "$USER" "$PROPNAME" watchers@example.org |
| 296 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/post-unlock.tmpl mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/post-unlock.tmpl |
| 297 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/post-unlock.tmpl 2006-08-26 23:59:56.000000000 +0200 |
| 298 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/post-unlock.tmpl 1970-01-01 01:00:00.000000000 +0100 |
| 299 |
@@ -1,42 +0,0 @@ |
| 300 |
-#!/bin/sh |
| 301 |
- |
| 302 |
-# POST-UNLOCK HOOK |
| 303 |
-# |
| 304 |
-# The post-unlock hook runs after a path is unlocked. Subversion runs |
| 305 |
-# this hook by invoking a program (script, executable, binary, etc.) |
| 306 |
-# named 'post-unlock' (for which this file is a template) with the |
| 307 |
-# following ordered arguments: |
| 308 |
-# |
| 309 |
-# [1] REPOS-PATH (the path to this repository) |
| 310 |
-# [2] USER (the user who destroyed the lock) |
| 311 |
-# |
| 312 |
-# The paths that were just unlocked are passed to the hook via STDIN |
| 313 |
-# (as of Subversion 1.2, only one path is passed per invocation, but |
| 314 |
-# the plan is to pass all unlocked paths at once, so the hook program |
| 315 |
-# should be written accordingly). |
| 316 |
-# |
| 317 |
-# The default working directory for the invocation is undefined, so |
| 318 |
-# the program should set one explicitly if it cares. |
| 319 |
-# |
| 320 |
-# Because the lock has already been destroyed and cannot be undone, |
| 321 |
-# the exit code of the hook program is ignored. |
| 322 |
-# |
| 323 |
-# On a Unix system, the normal procedure is to have 'post-unlock' |
| 324 |
-# invoke other programs to do the real work, though it may do the |
| 325 |
-# work itself too. |
| 326 |
-# |
| 327 |
-# Note that 'post-unlock' must be executable by the user(s) who will |
| 328 |
-# invoke it (typically the user httpd runs as), and that user must |
| 329 |
-# have filesystem-level permission to access the repository. |
| 330 |
-# |
| 331 |
-# On a Windows system, you should name the hook program |
| 332 |
-# 'post-unlock.bat' or 'post-unlock.exe', |
| 333 |
-# but the basic idea is the same. |
| 334 |
-# |
| 335 |
-# Here is an example hook script, for a Unix /bin/sh interpreter: |
| 336 |
- |
| 337 |
-REPOS="$1" |
| 338 |
-USER="$2" |
| 339 |
- |
| 340 |
-# Send email to interested parties, let them know a lock was removed: |
| 341 |
-mailer.py unlock "$REPOS" "$USER" /path/to/mailer.conf |
| 342 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/pre-commit.tmpl mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/pre-commit.tmpl |
| 343 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/pre-commit.tmpl 2006-08-26 23:59:56.000000000 +0200 |
| 344 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/pre-commit.tmpl 1970-01-01 01:00:00.000000000 +0100 |
| 345 |
@@ -1,70 +0,0 @@ |
| 346 |
-#!/bin/sh |
| 347 |
- |
| 348 |
-# PRE-COMMIT HOOK |
| 349 |
-# |
| 350 |
-# The pre-commit hook is invoked before a Subversion txn is |
| 351 |
-# committed. Subversion runs this hook by invoking a program |
| 352 |
-# (script, executable, binary, etc.) named 'pre-commit' (for which |
| 353 |
-# this file is a template), with the following ordered arguments: |
| 354 |
-# |
| 355 |
-# [1] REPOS-PATH (the path to this repository) |
| 356 |
-# [2] TXN-NAME (the name of the txn about to be committed) |
| 357 |
-# |
| 358 |
-# The default working directory for the invocation is undefined, so |
| 359 |
-# the program should set one explicitly if it cares. |
| 360 |
-# |
| 361 |
-# If the hook program exits with success, the txn is committed; but |
| 362 |
-# if it exits with failure (non-zero), the txn is aborted, no commit |
| 363 |
-# takes place, and STDERR is returned to the client. The hook |
| 364 |
-# program can use the 'svnlook' utility to help it examine the txn. |
| 365 |
-# |
| 366 |
-# On a Unix system, the normal procedure is to have 'pre-commit' |
| 367 |
-# invoke other programs to do the real work, though it may do the |
| 368 |
-# work itself too. |
| 369 |
-# |
| 370 |
-# *** NOTE: THE HOOK PROGRAM MUST NOT MODIFY THE TXN, EXCEPT *** |
| 371 |
-# *** FOR REVISION PROPERTIES (like svn:log or svn:author). *** |
| 372 |
-# |
| 373 |
-# This is why we recommend using the read-only 'svnlook' utility. |
| 374 |
-# In the future, Subversion may enforce the rule that pre-commit |
| 375 |
-# hooks should not modify the versioned data in txns, or else come |
| 376 |
-# up with a mechanism to make it safe to do so (by informing the |
| 377 |
-# committing client of the changes). However, right now neither |
| 378 |
-# mechanism is implemented, so hook writers just have to be careful. |
| 379 |
-# |
| 380 |
-# Note that 'pre-commit' must be executable by the user(s) who will |
| 381 |
-# invoke it (typically the user httpd runs as), and that user must |
| 382 |
-# have filesystem-level permission to access the repository. |
| 383 |
-# |
| 384 |
-# On a Windows system, you should name the hook program |
| 385 |
-# 'pre-commit.bat' or 'pre-commit.exe', |
| 386 |
-# but the basic idea is the same. |
| 387 |
-# |
| 388 |
-# The hook program typically does not inherit the environment of |
| 389 |
-# its parent process. For example, a common problem is for the |
| 390 |
-# PATH environment variable to not be set to its usual value, so |
| 391 |
-# that subprograms fail to launch unless invoked via absolute path. |
| 392 |
-# If you're having unexpected problems with a hook program, the |
| 393 |
-# culprit may be unusual (or missing) environment variables. |
| 394 |
-# |
| 395 |
-# Here is an example hook script, for a Unix /bin/sh interpreter. |
| 396 |
-# For more examples and pre-written hooks, see those in |
| 397 |
-# the Subversion repository at |
| 398 |
-# http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and |
| 399 |
-# http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/ |
| 400 |
- |
| 401 |
- |
| 402 |
-REPOS="$1" |
| 403 |
-TXN="$2" |
| 404 |
- |
| 405 |
-# Make sure that the log message contains some text. |
| 406 |
-SVNLOOK=/usr/bin/svnlook |
| 407 |
-$SVNLOOK log -t "$TXN" "$REPOS" | \ |
| 408 |
- grep "[a-zA-Z0-9]" > /dev/null || exit 1 |
| 409 |
- |
| 410 |
-# Check that the author of this commit has the rights to perform |
| 411 |
-# the commit on the files and directories being modified. |
| 412 |
-commit-access-control.pl "$REPOS" "$TXN" commit-access-control.cfg || exit 1 |
| 413 |
- |
| 414 |
-# All checks passed, so allow the commit. |
| 415 |
-exit 0 |
| 416 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/pre-lock.tmpl mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/pre-lock.tmpl |
| 417 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/pre-lock.tmpl 2006-08-26 23:59:56.000000000 +0200 |
| 418 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/pre-lock.tmpl 1970-01-01 01:00:00.000000000 +0100 |
| 419 |
@@ -1,64 +0,0 @@ |
| 420 |
-#!/bin/sh |
| 421 |
- |
| 422 |
-# PRE-LOCK HOOK |
| 423 |
-# |
| 424 |
-# The pre-lock hook is invoked before an exclusive lock is |
| 425 |
-# created. Subversion runs this hook by invoking a program |
| 426 |
-# (script, executable, binary, etc.) named 'pre-lock' (for which |
| 427 |
-# this file is a template), with the following ordered arguments: |
| 428 |
-# |
| 429 |
-# [1] REPOS-PATH (the path to this repository) |
| 430 |
-# [2] PATH (the path in the repository about to be locked) |
| 431 |
-# [3] USER (the user creating the lock) |
| 432 |
-# |
| 433 |
-# The default working directory for the invocation is undefined, so |
| 434 |
-# the program should set one explicitly if it cares. |
| 435 |
-# |
| 436 |
-# If the hook program exits with success, the lock is created; but |
| 437 |
-# if it exits with failure (non-zero), the lock action is aborted |
| 438 |
-# and STDERR is returned to the client. |
| 439 |
- |
| 440 |
-# On a Unix system, the normal procedure is to have 'pre-lock' |
| 441 |
-# invoke other programs to do the real work, though it may do the |
| 442 |
-# work itself too. |
| 443 |
-# |
| 444 |
-# Note that 'pre-lock' must be executable by the user(s) who will |
| 445 |
-# invoke it (typically the user httpd runs as), and that user must |
| 446 |
-# have filesystem-level permission to access the repository. |
| 447 |
-# |
| 448 |
-# On a Windows system, you should name the hook program |
| 449 |
-# 'pre-lock.bat' or 'pre-lock.exe', |
| 450 |
-# but the basic idea is the same. |
| 451 |
-# |
| 452 |
-# Here is an example hook script, for a Unix /bin/sh interpreter: |
| 453 |
- |
| 454 |
-REPOS="$1" |
| 455 |
-PATH="$2" |
| 456 |
-USER="$3" |
| 457 |
- |
| 458 |
-# If a lock exists and is owned by a different person, don't allow it |
| 459 |
-# to be stolen (e.g., with 'svn lock --force ...'). |
| 460 |
- |
| 461 |
-# (Maybe this script could send email to the lock owner?) |
| 462 |
-SVNLOOK=/usr/bin/svnlook |
| 463 |
-GREP=/bin/grep |
| 464 |
-SED=/bin/sed |
| 465 |
- |
| 466 |
-LOCK_OWNER=`$SVNLOOK lock "$REPOS" "$PATH" | \ |
| 467 |
- $GREP '^Owner: ' | $SED 's/Owner: //'` |
| 468 |
- |
| 469 |
-# If we get no result from svnlook, there's no lock, allow the lock to |
| 470 |
-# happen: |
| 471 |
-if [ "$LOCK_OWNER" == "" ]; then |
| 472 |
- exit 0 |
| 473 |
-fi |
| 474 |
- |
| 475 |
-# If the person locking matches the lock's owner, allow the lock to |
| 476 |
-# happen: |
| 477 |
-if [ "$LOCK_OWNER" == "$USER" ]; then |
| 478 |
- exit 0 |
| 479 |
-fi |
| 480 |
- |
| 481 |
-# Otherwise, we've got an owner mismatch, so return failure: |
| 482 |
-echo "Error: $PATH already locked by ${LOCK_OWNER}." 1>&2 |
| 483 |
-exit 1 |
| 484 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/pre-revprop-change.tmpl mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/pre-revprop-change.tmpl |
| 485 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/pre-revprop-change.tmpl 2006-08-26 23:59:56.000000000 +0200 |
| 486 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/pre-revprop-change.tmpl 1970-01-01 01:00:00.000000000 +0100 |
| 487 |
@@ -1,66 +0,0 @@ |
| 488 |
-#!/bin/sh |
| 489 |
- |
| 490 |
-# PRE-REVPROP-CHANGE HOOK |
| 491 |
-# |
| 492 |
-# The pre-revprop-change hook is invoked before a revision property |
| 493 |
-# is added, modified or deleted. Subversion runs this hook by invoking |
| 494 |
-# a program (script, executable, binary, etc.) named 'pre-revprop-change' |
| 495 |
-# (for which this file is a template), with the following ordered |
| 496 |
-# arguments: |
| 497 |
-# |
| 498 |
-# [1] REPOS-PATH (the path to this repository) |
| 499 |
-# [2] REVISION (the revision being tweaked) |
| 500 |
-# [3] USER (the username of the person tweaking the property) |
| 501 |
-# [4] PROPNAME (the property being set on the revision) |
| 502 |
-# [5] ACTION (the property is being 'A'dded, 'M'odified, or 'D'eleted) |
| 503 |
-# |
| 504 |
-# [STDIN] PROPVAL ** the new property value is passed via STDIN. |
| 505 |
-# |
| 506 |
-# If the hook program exits with success, the propchange happens; but |
| 507 |
-# if it exits with failure (non-zero), the propchange doesn't happen. |
| 508 |
-# The hook program can use the 'svnlook' utility to examine the |
| 509 |
-# existing value of the revision property. |
| 510 |
-# |
| 511 |
-# WARNING: unlike other hooks, this hook MUST exist for revision |
| 512 |
-# properties to be changed. If the hook does not exist, Subversion |
| 513 |
-# will behave as if the hook were present, but failed. The reason |
| 514 |
-# for this is that revision properties are UNVERSIONED, meaning that |
| 515 |
-# a successful propchange is destructive; the old value is gone |
| 516 |
-# forever. We recommend the hook back up the old value somewhere. |
| 517 |
-# |
| 518 |
-# On a Unix system, the normal procedure is to have 'pre-revprop-change' |
| 519 |
-# invoke other programs to do the real work, though it may do the |
| 520 |
-# work itself too. |
| 521 |
-# |
| 522 |
-# Note that 'pre-revprop-change' must be executable by the user(s) who will |
| 523 |
-# invoke it (typically the user httpd runs as), and that user must |
| 524 |
-# have filesystem-level permission to access the repository. |
| 525 |
-# |
| 526 |
-# On a Windows system, you should name the hook program |
| 527 |
-# 'pre-revprop-change.bat' or 'pre-revprop-change.exe', |
| 528 |
-# but the basic idea is the same. |
| 529 |
-# |
| 530 |
-# The hook program typically does not inherit the environment of |
| 531 |
-# its parent process. For example, a common problem is for the |
| 532 |
-# PATH environment variable to not be set to its usual value, so |
| 533 |
-# that subprograms fail to launch unless invoked via absolute path. |
| 534 |
-# If you're having unexpected problems with a hook program, the |
| 535 |
-# culprit may be unusual (or missing) environment variables. |
| 536 |
-# |
| 537 |
-# Here is an example hook script, for a Unix /bin/sh interpreter. |
| 538 |
-# For more examples and pre-written hooks, see those in |
| 539 |
-# the Subversion repository at |
| 540 |
-# http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and |
| 541 |
-# http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/ |
| 542 |
- |
| 543 |
- |
| 544 |
-REPOS="$1" |
| 545 |
-REV="$2" |
| 546 |
-USER="$3" |
| 547 |
-PROPNAME="$4" |
| 548 |
-ACTION="$5" |
| 549 |
- |
| 550 |
-if [ "$ACTION" = "M" -a "$PROPNAME" = "svn:log" ]; then exit 0; fi |
| 551 |
- |
| 552 |
-echo "Changing revision properties other than svn:log is prohibited" >&2 |
| 553 |
-exit 1 |
| 554 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/pre-unlock.tmpl mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/pre-unlock.tmpl |
| 555 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/pre-unlock.tmpl 2006-08-26 23:59:56.000000000 +0200 |
| 556 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/pre-unlock.tmpl 1970-01-01 01:00:00.000000000 +0100 |
| 557 |
@@ -1,60 +0,0 @@ |
| 558 |
-#!/bin/sh |
| 559 |
- |
| 560 |
-# PRE-UNLOCK HOOK |
| 561 |
-# |
| 562 |
-# The pre-unlock hook is invoked before an exclusive lock is |
| 563 |
-# destroyed. Subversion runs this hook by invoking a program |
| 564 |
-# (script, executable, binary, etc.) named 'pre-unlock' (for which |
| 565 |
-# this file is a template), with the following ordered arguments: |
| 566 |
-# |
| 567 |
-# [1] REPOS-PATH (the path to this repository) |
| 568 |
-# [2] PATH (the path in the repository about to be unlocked) |
| 569 |
-# [3] USER (the user destroying the lock) |
| 570 |
-# |
| 571 |
-# The default working directory for the invocation is undefined, so |
| 572 |
-# the program should set one explicitly if it cares. |
| 573 |
-# |
| 574 |
-# If the hook program exits with success, the lock is destroyed; but |
| 575 |
-# if it exits with failure (non-zero), the unlock action is aborted |
| 576 |
-# and STDERR is returned to the client. |
| 577 |
- |
| 578 |
-# On a Unix system, the normal procedure is to have 'pre-unlock' |
| 579 |
-# invoke other programs to do the real work, though it may do the |
| 580 |
-# work itself too. |
| 581 |
-# |
| 582 |
-# Note that 'pre-unlock' must be executable by the user(s) who will |
| 583 |
-# invoke it (typically the user httpd runs as), and that user must |
| 584 |
-# have filesystem-level permission to access the repository. |
| 585 |
-# |
| 586 |
-# On a Windows system, you should name the hook program |
| 587 |
-# 'pre-unlock.bat' or 'pre-unlock.exe', |
| 588 |
-# but the basic idea is the same. |
| 589 |
-# |
| 590 |
-# Here is an example hook script, for a Unix /bin/sh interpreter: |
| 591 |
- |
| 592 |
-REPOS="$1" |
| 593 |
-PATH="$2" |
| 594 |
-USER="$3" |
| 595 |
- |
| 596 |
-# If a lock is owned by a different person, don't allow it be broken. |
| 597 |
-# (Maybe this script could send email to the lock owner?) |
| 598 |
- |
| 599 |
-SVNLOOK=/usr/bin/svnlook |
| 600 |
-GREP=/bin/grep |
| 601 |
-SED=/bin/sed |
| 602 |
- |
| 603 |
-LOCK_OWNER=`$SVNLOOK lock "$REPOS" "$PATH" | \ |
| 604 |
- $GREP '^Owner: ' | $SED 's/Owner: //'` |
| 605 |
- |
| 606 |
-# If we get no result from svnlook, there's no lock, return success: |
| 607 |
-if [ "$LOCK_OWNER" == "" ]; then |
| 608 |
- exit 0 |
| 609 |
-fi |
| 610 |
-# If the person unlocking matches the lock's owner, return success: |
| 611 |
-if [ "$LOCK_OWNER" == "$USER" ]; then |
| 612 |
- exit 0 |
| 613 |
-fi |
| 614 |
- |
| 615 |
-# Otherwise, we've got an owner mismatch, so return failure: |
| 616 |
-echo "Error: $PATH locked by ${LOCK_OWNER}." 1>&2 |
| 617 |
-exit 1 |
| 618 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/start-commit.tmpl mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/start-commit.tmpl |
| 619 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/start-commit.tmpl 2006-08-26 23:59:56.000000000 +0200 |
| 620 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/hooks/start-commit.tmpl 1970-01-01 01:00:00.000000000 +0100 |
| 621 |
@@ -1,54 +0,0 @@ |
| 622 |
-#!/bin/sh |
| 623 |
- |
| 624 |
-# START-COMMIT HOOK |
| 625 |
-# |
| 626 |
-# The start-commit hook is invoked before a Subversion txn is created |
| 627 |
-# in the process of doing a commit. Subversion runs this hook |
| 628 |
-# by invoking a program (script, executable, binary, etc.) named |
| 629 |
-# 'start-commit' (for which this file is a template) |
| 630 |
-# with the following ordered arguments: |
| 631 |
-# |
| 632 |
-# [1] REPOS-PATH (the path to this repository) |
| 633 |
-# [2] USER (the authenticated user attempting to commit) |
| 634 |
-# |
| 635 |
-# The default working directory for the invocation is undefined, so |
| 636 |
-# the program should set one explicitly if it cares. |
| 637 |
-# |
| 638 |
-# If the hook program exits with success, the commit continues; but |
| 639 |
-# if it exits with failure (non-zero), the commit is stopped before |
| 640 |
-# a Subversion txn is created, and STDERR is returned to the client. |
| 641 |
-# |
| 642 |
-# On a Unix system, the normal procedure is to have 'start-commit' |
| 643 |
-# invoke other programs to do the real work, though it may do the |
| 644 |
-# work itself too. |
| 645 |
-# |
| 646 |
-# Note that 'start-commit' must be executable by the user(s) who will |
| 647 |
-# invoke it (typically the user httpd runs as), and that user must |
| 648 |
-# have filesystem-level permission to access the repository. |
| 649 |
-# |
| 650 |
-# On a Windows system, you should name the hook program |
| 651 |
-# 'start-commit.bat' or 'start-commit.exe', |
| 652 |
-# but the basic idea is the same. |
| 653 |
-# |
| 654 |
-# The hook program typically does not inherit the environment of |
| 655 |
-# its parent process. For example, a common problem is for the |
| 656 |
-# PATH environment variable to not be set to its usual value, so |
| 657 |
-# that subprograms fail to launch unless invoked via absolute path. |
| 658 |
-# If you're having unexpected problems with a hook program, the |
| 659 |
-# culprit may be unusual (or missing) environment variables. |
| 660 |
-# |
| 661 |
-# Here is an example hook script, for a Unix /bin/sh interpreter. |
| 662 |
-# For more examples and pre-written hooks, see those in |
| 663 |
-# the Subversion repository at |
| 664 |
-# http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and |
| 665 |
-# http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/ |
| 666 |
- |
| 667 |
- |
| 668 |
-REPOS="$1" |
| 669 |
-USER="$2" |
| 670 |
- |
| 671 |
-commit-allower.pl --repository "$REPOS" --user "$USER" || exit 1 |
| 672 |
-special-auth-check.py --user "$USER" --auth-level 3 || exit 1 |
| 673 |
- |
| 674 |
-# All checks passed, so allow the commit. |
| 675 |
-exit 0 |
| 676 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/locks/db.lock mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/locks/db.lock |
| 677 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/locks/db.lock 2006-08-26 23:59:59.000000000 +0200 |
| 678 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/locks/db.lock 1970-01-01 01:00:00.000000000 +0100 |
| 679 |
@@ -1,3 +0,0 @@ |
| 680 |
-This file is not used by Subversion 1.3.x or later. |
| 681 |
-However, its existence is required for compatibility with |
| 682 |
-Subversion 1.2.x or earlier. |
| 683 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/locks/db-logs.lock mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/locks/db-logs.lock |
| 684 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/locks/db-logs.lock 2006-08-26 23:59:59.000000000 +0200 |
| 685 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/locks/db-logs.lock 1970-01-01 01:00:00.000000000 +0100 |
| 686 |
@@ -1,3 +0,0 @@ |
| 687 |
-This file is not used by Subversion 1.3.x or later. |
| 688 |
-However, its existence is required for compatibility with |
| 689 |
-Subversion 1.2.x or earlier. |
| 690 |
diff -Nur -x '*.orig' -x '*.rej' smeserver-subversion-1.2/root/etc/e-smith/skel/repository/README.txt mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/README.txt |
| 691 |
--- smeserver-subversion-1.2/root/etc/e-smith/skel/repository/README.txt 2006-08-26 23:59:59.000000000 +0200 |
| 692 |
+++ mezzanine_patched_smeserver-subversion-1.2/root/etc/e-smith/skel/repository/README.txt 1970-01-01 01:00:00.000000000 +0100 |
| 693 |
@@ -1,5 +0,0 @@ |
| 694 |
-This is a Subversion repository; use the 'svnadmin' tool to examine |
| 695 |
-it. Do not add, delete, or modify files here unless you know how |
| 696 |
-to avoid corrupting the repository. |
| 697 |
- |
| 698 |
-Visit http://subversion.tigris.org/ for more information. |
Parent Directory
| 
Revision Log
| 
Revision Graph
