svnroot/0000775000175000017500000000000010314766354012163 5ustar doudoudoudousvnroot/locks/0000775000175000017500000000000010314766353013275 5ustar doudoudoudousvnroot/locks/db.lock0000664000175000017500000000071410314466413014530 0ustar doudoudoudouDB lock file, representing locks on the versioned filesystem. All accessors -- both readers and writers -- of the repository's Berkeley DB environment take out shared locks on this file, and each accessor removes its lock when done. If and when the DB recovery procedure is run, the recovery code takes out an exclusive lock on this file, so we can be sure no one else is using the DB during the recovery. You should never have to edit or remove this file. svnroot/locks/db-logs.lock0000664000175000017500000000044710314466413015475 0ustar doudoudoudouDB logs lock file, representing locks on the versioned filesystem logs. All log manipulators of the repository's Berkeley DB environment take out exclusive locks on this file to ensure that only one accessor manupulates the logs at the time. You should never have to edit or remove this file. svnroot/locks/CVS/0000775000175000017500000000000010314766033013723 5ustar doudoudoudousvnroot/locks/CVS/Root0000664000175000017500000000005610314765713014576 0ustar doudoudoudou:ext:lapinot@rubyforge.org:/var/cvs/autobuild svnroot/locks/CVS/Repository0000664000175000017500000000004210314765713016025 0ustar doudoudoudouautobuild/test/data/svnroot/locks svnroot/locks/CVS/Entries0000664000175000017500000000011110314766033015250 0ustar doudoudoudouD/CVS//// /db.lock/0/dummy timestamp// /db-logs.lock/0/dummy timestamp// svnroot/locks/CVS/CVS/0000775000175000017500000000000010314766033014356 5ustar doudoudoudousvnroot/locks/CVS/CVS/Root0000664000175000017500000000005610314766033015225 0ustar doudoudoudou:ext:lapinot@rubyforge.org:/var/cvs/autobuild svnroot/locks/CVS/CVS/Repository0000664000175000017500000000004610314766033016460 0ustar doudoudoudouautobuild/test/data/svnroot/locks/CVS svnroot/locks/CVS/CVS/Entries0000664000175000017500000000000210314766033015702 0ustar doudoudoudouD svnroot/locks/.#db-logs.lock.00000664000175000017500000000044710314466413015754 0ustar doudoudoudouDB logs lock file, representing locks on the versioned filesystem logs. All log manipulators of the repository's Berkeley DB environment take out exclusive locks on this file to ensure that only one accessor manupulates the logs at the time. You should never have to edit or remove this file. svnroot/locks/.#db.lock.00000664000175000017500000000071410314466413015007 0ustar doudoudoudouDB lock file, representing locks on the versioned filesystem. All accessors -- both readers and writers -- of the repository's Berkeley DB environment take out shared locks on this file, and each accessor removes its lock when done. If and when the DB recovery procedure is run, the recovery code takes out an exclusive lock on this file, so we can be sure no one else is using the DB during the recovery. You should never have to edit or remove this file. svnroot/hooks/0000775000175000017500000000000010314766353013305 5ustar doudoudoudousvnroot/hooks/start-commit.tmpl0000664000175000017500000000413010314466413016616 0ustar doudoudoudou#!/bin/sh # START-COMMIT HOOK # # The start-commit hook is invoked before a Subversion txn is created # in the process of doing a commit. Subversion runs this hook # by invoking a program (script, executable, binary, etc.) named # 'start-commit' (for which this file is a template) # with the following ordered arguments: # # [1] REPOS-PATH (the path to this repository) # [2] USER (the authenticated user attempting to commit) # # The default working directory for the invocation is undefined, so # the program should set one explicitly if it cares. # # If the hook program exits with success, the commit continues; but # if it exits with failure (non-zero), the commit is stopped before # a Subversion txn is created, and STDERR is returned to the client. # # On a Unix system, the normal procedure is to have 'start-commit' # invoke other programs to do the real work, though it may do the # work itself too. # # Note that 'start-commit' must be executable by the user(s) who will # invoke it (typically the user httpd runs as), and that user must # have filesystem-level permission to access the repository. # # On a Windows system, you should name the hook program # 'start-commit.bat' or 'start-commit.exe', # but the basic idea is the same. # # The hook program typically does not inherit the environment of # its parent process. For example, a common problem is for the # PATH environment variable to not be set to its usual value, so # that subprograms fail to launch unless invoked via absolute path. # If you're having unexpected problems with a hook program, the # culprit may be unusual (or missing) environment variables. # # Here is an example hook script, for a Unix /bin/sh interpreter.# For more examples and pre-written hooks, see those in # the Subversion repository at # http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and # http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/ REPOS="$1" USER="$2" commit-allower.pl --repository "$REPOS" --user "$USER" || exit 1 special-auth-check.py --user "$USER" --auth-level 3 || exit 1 # All checks passed, so allow the commit. exit 0 svnroot/hooks/pre-commit.tmpl0000664000175000017500000000562610314466413016262 0ustar doudoudoudou#!/bin/sh # PRE-COMMIT HOOK # # The pre-commit hook is invoked before a Subversion txn is # committed. Subversion runs this hook by invoking a program # (script, executable, binary, etc.) named 'pre-commit' (for which # this file is a template), with the following ordered arguments: # # [1] REPOS-PATH (the path to this repository) # [2] TXN-NAME (the name of the txn about to be committed) # # The default working directory for the invocation is undefined, so # the program should set one explicitly if it cares. # # If the hook program exits with success, the txn is committed; but # if it exits with failure (non-zero), the txn is aborted, no commit # takes place, and STDERR is returned to the client. The hook # program can use the 'svnlook' utility to help it examine the txn. # # On a Unix system, the normal procedure is to have 'pre-commit' # invoke other programs to do the real work, though it may do the # work itself too. # # *** NOTE: THE HOOK PROGRAM MUST NOT MODIFY THE TXN, EXCEPT *** # *** FOR REVISION PROPERTIES (like svn:log or svn:author). *** # # This is why we recommend using the read-only 'svnlook' utility. # In the future, Subversion may enforce the rule that pre-commit # hooks should not modify the versioned data in txns, or else come # up with a mechanism to make it safe to do so (by informing the # committing client of the changes). However, right now neither # mechanism is implemented, so hook writers just have to be careful. # # Note that 'pre-commit' must be executable by the user(s) who will # invoke it (typically the user httpd runs as), and that user must # have filesystem-level permission to access the repository. # # On a Windows system, you should name the hook program # 'pre-commit.bat' or 'pre-commit.exe', # but the basic idea is the same. # # The hook program typically does not inherit the environment of # its parent process. For example, a common problem is for the # PATH environment variable to not be set to its usual value, so # that subprograms fail to launch unless invoked via absolute path. # If you're having unexpected problems with a hook program, the # culprit may be unusual (or missing) environment variables. # # Here is an example hook script, for a Unix /bin/sh interpreter.# For more examples and pre-written hooks, see those in # the Subversion repository at # http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and # http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/ REPOS="$1" TXN="$2" # Make sure that the log message contains some text. SVNLOOK=/usr/bin/svnlook $SVNLOOK log -t "$TXN" "$REPOS" | \ grep "[a-zA-Z0-9]" > /dev/null || exit 1 # Check that the author of this commit has the rights to perform # the commit on the files and directories being modified. /usr/lib/subversion/hook-scripts/commit-access-control.pl "$REPOS" "$TXN" commit-access-control.cfg || exit 1 # All checks passed, so allow the commit. exit 0 svnroot/hooks/pre-revprop-change.tmpl0000664000175000017500000000531310314466413017703 0ustar doudoudoudou#!/bin/sh # PRE-REVPROP-CHANGE HOOK # # The pre-revprop-change hook is invoked before a revision property # is added, modified or deleted. Subversion runs this hook by invoking # a program (script, executable, binary, etc.) named 'pre-revprop-change' # (for which this file is a template), with the following ordered # arguments: # # [1] REPOS-PATH (the path to this repository) # [2] REVISION (the revision being tweaked) # [3] USER (the username of the person tweaking the property) # [4] PROPNAME (the property being set on the revision) # [5] ACTION (the property is being 'A'dded, 'M'odified, or 'D'eleted) # # [STDIN] PROPVAL ** the new property value is passed via STDIN. # # If the hook program exits with success, the propchange happens; but # if it exits with failure (non-zero), the propchange doesn't happen. # The hook program can use the 'svnlook' utility to examine the # existing value of the revision property. # # WARNING: unlike other hooks, this hook MUST exist for revision # properties to be changed. If the hook does not exist, Subversion # will behave as if the hook were present, but failed. The reason # for this is that revision properties are UNVERSIONED, meaning that # a successful propchange is destructive; the old value is gone # forever. We recommend the hook back up the old value somewhere. # # On a Unix system, the normal procedure is to have 'pre-revprop-change' # invoke other programs to do the real work, though it may do the # work itself too. # # Note that 'pre-revprop-change' must be executable by the user(s) who will # invoke it (typically the user httpd runs as), and that user must # have filesystem-level permission to access the repository. # # On a Windows system, you should name the hook program # 'pre-revprop-change.bat' or 'pre-revprop-change.exe', # but the basic idea is the same. # # The hook program typically does not inherit the environment of # its parent process. For example, a common problem is for the # PATH environment variable to not be set to its usual value, so # that subprograms fail to launch unless invoked via absolute path. # If you're having unexpected problems with a hook program, the # culprit may be unusual (or missing) environment variables. # # Here is an example hook script, for a Unix /bin/sh interpreter.# For more examples and pre-written hooks, see those in # the Subversion repository at # http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and # http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/ REPOS="$1" REV="$2" USER="$3" PROPNAME="$4" ACTION="$5" if [ "$ACTION" = "M" -a "$PROPNAME" = "svn:log" ]; then exit 0; fi echo "Changing revision properties other than svn:log is prohibited" >&2 exit 1 svnroot/hooks/pre-lock.tmpl0000664000175000017500000000373110314466413015715 0ustar doudoudoudou#!/bin/sh # PRE-LOCK HOOK # # The pre-lock hook is invoked before an exclusive lock is # created. Subversion runs this hook by invoking a program # (script, executable, binary, etc.) named 'pre-lock' (for which # this file is a template), with the following ordered arguments: # # [1] REPOS-PATH (the path to this repository) # [2] PATH (the path in the repository about to be locked) # [3] USER (the user creating the lock) # # The default working directory for the invocation is undefined, so # the program should set one explicitly if it cares. # # If the hook program exits with success, the lock is created; but # if it exits with failure (non-zero), the lock action is aborted # and STDERR is returned to the client. # On a Unix system, the normal procedure is to have 'pre-lock' # invoke other programs to do the real work, though it may do the # work itself too. # # Note that 'pre-lock' must be executable by the user(s) who will # invoke it (typically the user httpd runs as), and that user must # have filesystem-level permission to access the repository. # # On a Windows system, you should name the hook program # 'pre-lock.bat' or 'pre-lock.exe', # but the basic idea is the same. # # Here is an example hook script, for a Unix /bin/sh interpreter: REPOS="$1" PATH="$2" USER="$3" # If a lock exists and is owned by a different person, don't allow it # to be broken. # (Maybe this script could send email to the to the lock owner?) SVNLOOK=/usr/binsvnlook GREP=/bin/grep SED=/bin/sed LOCK_OWNER=`$SVNLOOK lock "$REPOS" "$PATH" | \ $GREP '^Owner:' | $SED 's/Owner: //'` # If we get no result from svnlook, there's no lock, allow the lock to # happen: if [ "$LOCK_OWNER" == "" ]; then exit 0 fi # If the person locking matches the lock's owner, allow the lock to # happen: if [ "$LOCK_OWNER" == "$USER" ]; then exit 0 fi # Otherwise, we've got an owner mismatch, so return failure: echo "Error: $PATH already locked by ${LOCK_OWNER}." 1>&2 exit 1 svnroot/hooks/pre-unlock.tmpl0000664000175000017500000000370410314466413016260 0ustar doudoudoudou#!/bin/sh # PRE-UNLOCK HOOK # # The pre-unlock hook is invoked before an exclusive lock is # destroyed. Subversion runs this hook by invoking a program # (script, executable, binary, etc.) named 'pre-unlock' (for which # this file is a template), with the following ordered arguments: # # [1] REPOS-PATH (the path to this repository) # [2] PATH (the path in the repository about to be unlocked) # [3] USER (the user destroying the lock) # # The default working directory for the invocation is undefined, so # the program should set one explicitly if it cares. # # If the hook program exits with success, the lock is destroyed; but # if it exits with failure (non-zero), the unlock action is aborted # and STDERR is returned to the client. # On a Unix system, the normal procedure is to have 'pre-unlock' # invoke other programs to do the real work, though it may do the # work itself too. # # Note that 'pre-unlock' must be executable by the user(s) who will # invoke it (typically the user httpd runs as), and that user must # have filesystem-level permission to access the repository. # # On a Windows system, you should name the hook program # 'pre-unlock.bat' or 'pre-unlock.exe', # but the basic idea is the same. # # Here is an example hook script, for a Unix /bin/sh interpreter: REPOS="$1" PATH="$2" USER="$3" # If a lock is owned by a different person, don't allow it be broken. # (Maybe this script could send email to the to the lock owner?) SVNLOOK=/usr/bin/svnlook GREP=/bin/grep SED=/bin/sed LOCK_OWNER=`$SVNLOOK lock "$REPOS" "$PATH" | \ $GREP '^Owner: ' | $SED 's/Owner: //'` # If we get no result from svnlook, there's no lock, return success: if [ "$LOCK_OWNER" == "" ]; then exit 0 fi # If the person unlocking matches the lock's owner, return success: if [ "$LOCK_OWNER" == "$USER" ]; then exit 0 fi # Otherwise, we've got an owner mismatch, so return failure: echo "Error: $PATH locked by ${LOCK_OWNER}." 1>&2 exit 1 svnroot/hooks/post-commit.tmpl0000664000175000017500000000371110314466413016452 0ustar doudoudoudou#!/bin/sh # POST-COMMIT HOOK # # The post-commit hook is invoked after a commit. Subversion runs # this hook by invoking a program (script, executable, binary, etc.) # named 'post-commit' (for which this file is a template) with the # following ordered arguments: # # [1] REPOS-PATH (the path to this repository) # [2] REV (the number of the revision just committed) # # The default working directory for the invocation is undefined, so # the program should set one explicitly if it cares. # # Because the commit has already completed and cannot be undone, # the exit code of the hook program is ignored. The hook program # can use the 'svnlook' utility to help it examine the # newly-committed tree. # # On a Unix system, the normal procedure is to have 'post-commit' # invoke other programs to do the real work, though it may do the # work itself too. # # Note that 'post-commit' must be executable by the user(s) who will # invoke it (typically the user httpd runs as), and that user must # have filesystem-level permission to access the repository. # # On a Windows system, you should name the hook program # 'post-commit.bat' or 'post-commit.exe', # but the basic idea is the same. # # The hook program typically does not inherit the environment of # its parent process. For example, a common problem is for the # PATH environment variable to not be set to its usual value, so # that subprograms fail to launch unless invoked via absolute path. # If you're having unexpected problems with a hook program, the # culprit may be unusual (or missing) environment variables. # # Here is an example hook script, for a Unix /bin/sh interpreter.# For more examples and pre-written hooks, see those in # the Subversion repository at # http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and # http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/ REPOS="$1" REV="$2" /usr/lib/subversion/hook-scripts/commit-email.pl "$REPOS" "$REV" commit-watchers@example.org svnroot/hooks/post-lock.tmpl0000664000175000017500000000316010314466413016110 0ustar doudoudoudou#!/bin/sh # POST-LOCK HOOK # # The post-lock hook is run after a path is locked. Subversion runs # this hook by invoking a program (script, executable, binary, etc.) # named 'post-lock' (for which this file is a template) with the # following ordered arguments: # # [1] REPOS-PATH (the path to this repository) # [2] USER (the user who created the lock) # # The paths that were just locked are passed to the hook via STDIN (As # of Subversion 1.2, only one path is passed per invocation, but the # plan is to pass all locked paths at once in Subversion 1.3 and # later). # # The default working directory for the invocation is undefined, so # the program should set one explicitly if it cares. # # Because the lock has already been created and cannot be undone, # the exit code of the hook program is ignored. The hook program # can use the 'svnlook' utility to help it examine the # newly-created lock. # # On a Unix system, the normal procedure is to have 'post-lock' # invoke other programs to do the real work, though it may do the # work itself too. # # Note that 'post-lock' must be executable by the user(s) who will # invoke it (typically the user httpd runs as), and that user must # have filesystem-level permission to access the repository. # # On a Windows system, you should name the hook program # 'post-lock.bat' or 'post-lock.exe', # but the basic idea is the same. # # Here is an example hook script, for a Unix /bin/sh interpreter: REPOS="$1" USER="$2" # Send email to interested parties, let them know a lock was created: /usr/lib/subversion/hook-scripts/mailer.py lock "$REPOS" "$USER" /path/to/mailer.conf svnroot/hooks/post-unlock.tmpl0000664000175000017500000000304710314466413016457 0ustar doudoudoudou#!/bin/sh # POST-UNLOCK HOOK # # The post-unlock hook runs after a path is unlocked. Subversion runs # this hook by invoking a program (script, executable, binary, etc.) # named 'post-unlock' (for which this file is a template) with the # following ordered arguments: # # [1] REPOS-PATH (the path to this repository) # [2] USER (the user who destroyed the lock) # # The paths that were just unlocked are passed to the hook via STDIN # (As of Subversion 1.2, only one path is passed per invocation, but # the plan is to pass all locked paths at once in Subversion 1.3 and # later). # # The default working directory for the invocation is undefined, so # the program should set one explicitly if it cares. # # Because the lock has already been destroyed and cannot be undone, # the exit code of the hook program is ignored. # # On a Unix system, the normal procedure is to have 'post-unlock' # invoke other programs to do the real work, though it may do the # work itself too. # # Note that 'post-unlock' must be executable by the user(s) who will # invoke it (typically the user httpd runs as), and that user must # have filesystem-level permission to access the repository. # # On a Windows system, you should name the hook program # 'post-unlock.bat' or 'post-unlock.exe', # but the basic idea is the same. # # Here is an example hook script, for a Unix /bin/sh interpreter: REPOS="$1" USER="$2" # Send email to interested parties, let them know a lock was removed: /usr/lib/subversion/hook-scripts/mailer.py unlock "$REPOS" "$USER" /path/to/mailer.conf svnroot/hooks/post-revprop-change.tmpl0000664000175000017500000000435710314466413020111 0ustar doudoudoudou#!/bin/sh # POST-REVPROP-CHANGE HOOK # # The post-revprop-change hook is invoked after a revision property # has been added, modified or deleted. Subversion runs this hook by # invoking a program (script, executable, binary, etc.) named # 'post-revprop-change' (for which this file is a template), with the # following ordered arguments: # # [1] REPOS-PATH (the path to this repository) # [2] REV (the revision that was tweaked) # [3] USER (the username of the person tweaking the property) # [4] PROPNAME (the property that was changed) # [5] ACTION (the property was 'A'dded, 'M'odified, or 'D'eleted) # # [STDIN] PROPVAL ** the old property value is passed via STDIN. # # Because the propchange has already completed and cannot be undone, # the exit code of the hook program is ignored. The hook program # can use the 'svnlook' utility to help it examine the # new property value. # # On a Unix system, the normal procedure is to have 'post-revprop-change' # invoke other programs to do the real work, though it may do the # work itself too. # # Note that 'post-revprop-change' must be executable by the user(s) who will # invoke it (typically the user httpd runs as), and that user must # have filesystem-level permission to access the repository. # # On a Windows system, you should name the hook program # 'post-revprop-change.bat' or 'post-revprop-change.exe', # but the basic idea is the same. # # The hook program typically does not inherit the environment of # its parent process. For example, a common problem is for the # PATH environment variable to not be set to its usual value, so # that subprograms fail to launch unless invoked via absolute path. # If you're having unexpected problems with a hook program, the # culprit may be unusual (or missing) environment variables. # # Here is an example hook script, for a Unix /bin/sh interpreter.# For more examples and pre-written hooks, see those in # the Subversion repository at # http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and # http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/ REPOS="$1" REV="$2" USER="$3" PROPNAME="$4" ACTION="$5" /usr/lib/subversion/hook-scripts/propchange-email.pl "$REPOS" "$REV" "$USER" "$PROPNAME" watchers@example.org svnroot/hooks/CVS/0000775000175000017500000000000010314766033013733 5ustar doudoudoudousvnroot/hooks/CVS/Root0000664000175000017500000000005610314765713014606 0ustar doudoudoudou:ext:lapinot@rubyforge.org:/var/cvs/autobuild svnroot/hooks/CVS/Repository0000664000175000017500000000004210314765713016035 0ustar doudoudoudouautobuild/test/data/svnroot/hooks svnroot/hooks/CVS/Entries0000664000175000017500000000055110314766033015270 0ustar doudoudoudouD/CVS//// /post-commit.tmpl/0/dummy timestamp// /post-lock.tmpl/0/dummy timestamp// /post-revprop-change.tmpl/0/dummy timestamp// /post-unlock.tmpl/0/dummy timestamp// /pre-commit.tmpl/0/dummy timestamp// /pre-lock.tmpl/0/dummy timestamp// /pre-revprop-change.tmpl/0/dummy timestamp// /pre-unlock.tmpl/0/dummy timestamp// /start-commit.tmpl/0/dummy timestamp// svnroot/hooks/CVS/CVS/0000775000175000017500000000000010314766033014366 5ustar doudoudoudousvnroot/hooks/CVS/CVS/Root0000664000175000017500000000005610314766033015235 0ustar doudoudoudou:ext:lapinot@rubyforge.org:/var/cvs/autobuild svnroot/hooks/CVS/CVS/Repository0000664000175000017500000000004610314766033016470 0ustar doudoudoudouautobuild/test/data/svnroot/hooks/CVS svnroot/hooks/CVS/CVS/Entries0000664000175000017500000000000210314766033015712 0ustar doudoudoudouD svnroot/hooks/.#post-commit.tmpl.00000664000175000017500000000371110314466413016731 0ustar doudoudoudou#!/bin/sh # POST-COMMIT HOOK # # The post-commit hook is invoked after a commit. Subversion runs # this hook by invoking a program (script, executable, binary, etc.) # named 'post-commit' (for which this file is a template) with the # following ordered arguments: # # [1] REPOS-PATH (the path to this repository) # [2] REV (the number of the revision just committed) # # The default working directory for the invocation is undefined, so # the program should set one explicitly if it cares. # # Because the commit has already completed and cannot be undone, # the exit code of the hook program is ignored. The hook program # can use the 'svnlook' utility to help it examine the # newly-committed tree. # # On a Unix system, the normal procedure is to have 'post-commit' # invoke other programs to do the real work, though it may do the # work itself too. # # Note that 'post-commit' must be executable by the user(s) who will # invoke it (typically the user httpd runs as), and that user must # have filesystem-level permission to access the repository. # # On a Windows system, you should name the hook program # 'post-commit.bat' or 'post-commit.exe', # but the basic idea is the same. # # The hook program typically does not inherit the environment of # its parent process. For example, a common problem is for the # PATH environment variable to not be set to its usual value, so # that subprograms fail to launch unless invoked via absolute path. # If you're having unexpected problems with a hook program, the # culprit may be unusual (or missing) environment variables. # # Here is an example hook script, for a Unix /bin/sh interpreter.# For more examples and pre-written hooks, see those in # the Subversion repository at # http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and # http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/ REPOS="$1" REV="$2" /usr/lib/subversion/hook-scripts/commit-email.pl "$REPOS" "$REV" commit-watchers@example.org svnroot/hooks/.#post-lock.tmpl.00000664000175000017500000000316010314466413016367 0ustar doudoudoudou#!/bin/sh # POST-LOCK HOOK # # The post-lock hook is run after a path is locked. Subversion runs # this hook by invoking a program (script, executable, binary, etc.) # named 'post-lock' (for which this file is a template) with the # following ordered arguments: # # [1] REPOS-PATH (the path to this repository) # [2] USER (the user who created the lock) # # The paths that were just locked are passed to the hook via STDIN (As # of Subversion 1.2, only one path is passed per invocation, but the # plan is to pass all locked paths at once in Subversion 1.3 and # later). # # The default working directory for the invocation is undefined, so # the program should set one explicitly if it cares. # # Because the lock has already been created and cannot be undone, # the exit code of the hook program is ignored. The hook program # can use the 'svnlook' utility to help it examine the # newly-created lock. # # On a Unix system, the normal procedure is to have 'post-lock' # invoke other programs to do the real work, though it may do the # work itself too. # # Note that 'post-lock' must be executable by the user(s) who will # invoke it (typically the user httpd runs as), and that user must # have filesystem-level permission to access the repository. # # On a Windows system, you should name the hook program # 'post-lock.bat' or 'post-lock.exe', # but the basic idea is the same. # # Here is an example hook script, for a Unix /bin/sh interpreter: REPOS="$1" USER="$2" # Send email to interested parties, let them know a lock was created: /usr/lib/subversion/hook-scripts/mailer.py lock "$REPOS" "$USER" /path/to/mailer.conf svnroot/hooks/.#post-revprop-change.tmpl.00000664000175000017500000000435710314466413020370 0ustar doudoudoudou#!/bin/sh # POST-REVPROP-CHANGE HOOK # # The post-revprop-change hook is invoked after a revision property # has been added, modified or deleted. Subversion runs this hook by # invoking a program (script, executable, binary, etc.) named # 'post-revprop-change' (for which this file is a template), with the # following ordered arguments: # # [1] REPOS-PATH (the path to this repository) # [2] REV (the revision that was tweaked) # [3] USER (the username of the person tweaking the property) # [4] PROPNAME (the property that was changed) # [5] ACTION (the property was 'A'dded, 'M'odified, or 'D'eleted) # # [STDIN] PROPVAL ** the old property value is passed via STDIN. # # Because the propchange has already completed and cannot be undone, # the exit code of the hook program is ignored. The hook program # can use the 'svnlook' utility to help it examine the # new property value. # # On a Unix system, the normal procedure is to have 'post-revprop-change' # invoke other programs to do the real work, though it may do the # work itself too. # # Note that 'post-revprop-change' must be executable by the user(s) who will # invoke it (typically the user httpd runs as), and that user must # have filesystem-level permission to access the repository. # # On a Windows system, you should name the hook program # 'post-revprop-change.bat' or 'post-revprop-change.exe', # but the basic idea is the same. # # The hook program typically does not inherit the environment of # its parent process. For example, a common problem is for the # PATH environment variable to not be set to its usual value, so # that subprograms fail to launch unless invoked via absolute path. # If you're having unexpected problems with a hook program, the # culprit may be unusual (or missing) environment variables. # # Here is an example hook script, for a Unix /bin/sh interpreter.# For more examples and pre-written hooks, see those in # the Subversion repository at # http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and # http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/ REPOS="$1" REV="$2" USER="$3" PROPNAME="$4" ACTION="$5" /usr/lib/subversion/hook-scripts/propchange-email.pl "$REPOS" "$REV" "$USER" "$PROPNAME" watchers@example.org svnroot/hooks/.#post-unlock.tmpl.00000664000175000017500000000304710314466413016736 0ustar doudoudoudou#!/bin/sh # POST-UNLOCK HOOK # # The post-unlock hook runs after a path is unlocked. Subversion runs # this hook by invoking a program (script, executable, binary, etc.) # named 'post-unlock' (for which this file is a template) with the # following ordered arguments: # # [1] REPOS-PATH (the path to this repository) # [2] USER (the user who destroyed the lock) # # The paths that were just unlocked are passed to the hook via STDIN # (As of Subversion 1.2, only one path is passed per invocation, but # the plan is to pass all locked paths at once in Subversion 1.3 and # later). # # The default working directory for the invocation is undefined, so # the program should set one explicitly if it cares. # # Because the lock has already been destroyed and cannot be undone, # the exit code of the hook program is ignored. # # On a Unix system, the normal procedure is to have 'post-unlock' # invoke other programs to do the real work, though it may do the # work itself too. # # Note that 'post-unlock' must be executable by the user(s) who will # invoke it (typically the user httpd runs as), and that user must # have filesystem-level permission to access the repository. # # On a Windows system, you should name the hook program # 'post-unlock.bat' or 'post-unlock.exe', # but the basic idea is the same. # # Here is an example hook script, for a Unix /bin/sh interpreter: REPOS="$1" USER="$2" # Send email to interested parties, let them know a lock was removed: /usr/lib/subversion/hook-scripts/mailer.py unlock "$REPOS" "$USER" /path/to/mailer.conf svnroot/hooks/.#pre-commit.tmpl.00000664000175000017500000000562610314466413016541 0ustar doudoudoudou#!/bin/sh # PRE-COMMIT HOOK # # The pre-commit hook is invoked before a Subversion txn is # committed. Subversion runs this hook by invoking a program # (script, executable, binary, etc.) named 'pre-commit' (for which # this file is a template), with the following ordered arguments: # # [1] REPOS-PATH (the path to this repository) # [2] TXN-NAME (the name of the txn about to be committed) # # The default working directory for the invocation is undefined, so # the program should set one explicitly if it cares. # # If the hook program exits with success, the txn is committed; but # if it exits with failure (non-zero), the txn is aborted, no commit # takes place, and STDERR is returned to the client. The hook # program can use the 'svnlook' utility to help it examine the txn. # # On a Unix system, the normal procedure is to have 'pre-commit' # invoke other programs to do the real work, though it may do the # work itself too. # # *** NOTE: THE HOOK PROGRAM MUST NOT MODIFY THE TXN, EXCEPT *** # *** FOR REVISION PROPERTIES (like svn:log or svn:author). *** # # This is why we recommend using the read-only 'svnlook' utility. # In the future, Subversion may enforce the rule that pre-commit # hooks should not modify the versioned data in txns, or else come # up with a mechanism to make it safe to do so (by informing the # committing client of the changes). However, right now neither # mechanism is implemented, so hook writers just have to be careful. # # Note that 'pre-commit' must be executable by the user(s) who will # invoke it (typically the user httpd runs as), and that user must # have filesystem-level permission to access the repository. # # On a Windows system, you should name the hook program # 'pre-commit.bat' or 'pre-commit.exe', # but the basic idea is the same. # # The hook program typically does not inherit the environment of # its parent process. For example, a common problem is for the # PATH environment variable to not be set to its usual value, so # that subprograms fail to launch unless invoked via absolute path. # If you're having unexpected problems with a hook program, the # culprit may be unusual (or missing) environment variables. # # Here is an example hook script, for a Unix /bin/sh interpreter.# For more examples and pre-written hooks, see those in # the Subversion repository at # http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and # http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/ REPOS="$1" TXN="$2" # Make sure that the log message contains some text. SVNLOOK=/usr/bin/svnlook $SVNLOOK log -t "$TXN" "$REPOS" | \ grep "[a-zA-Z0-9]" > /dev/null || exit 1 # Check that the author of this commit has the rights to perform # the commit on the files and directories being modified. /usr/lib/subversion/hook-scripts/commit-access-control.pl "$REPOS" "$TXN" commit-access-control.cfg || exit 1 # All checks passed, so allow the commit. exit 0 svnroot/hooks/.#pre-lock.tmpl.00000664000175000017500000000373110314466413016174 0ustar doudoudoudou#!/bin/sh # PRE-LOCK HOOK # # The pre-lock hook is invoked before an exclusive lock is # created. Subversion runs this hook by invoking a program # (script, executable, binary, etc.) named 'pre-lock' (for which # this file is a template), with the following ordered arguments: # # [1] REPOS-PATH (the path to this repository) # [2] PATH (the path in the repository about to be locked) # [3] USER (the user creating the lock) # # The default working directory for the invocation is undefined, so # the program should set one explicitly if it cares. # # If the hook program exits with success, the lock is created; but # if it exits with failure (non-zero), the lock action is aborted # and STDERR is returned to the client. # On a Unix system, the normal procedure is to have 'pre-lock' # invoke other programs to do the real work, though it may do the # work itself too. # # Note that 'pre-lock' must be executable by the user(s) who will # invoke it (typically the user httpd runs as), and that user must # have filesystem-level permission to access the repository. # # On a Windows system, you should name the hook program # 'pre-lock.bat' or 'pre-lock.exe', # but the basic idea is the same. # # Here is an example hook script, for a Unix /bin/sh interpreter: REPOS="$1" PATH="$2" USER="$3" # If a lock exists and is owned by a different person, don't allow it # to be broken. # (Maybe this script could send email to the to the lock owner?) SVNLOOK=/usr/binsvnlook GREP=/bin/grep SED=/bin/sed LOCK_OWNER=`$SVNLOOK lock "$REPOS" "$PATH" | \ $GREP '^Owner:' | $SED 's/Owner: //'` # If we get no result from svnlook, there's no lock, allow the lock to # happen: if [ "$LOCK_OWNER" == "" ]; then exit 0 fi # If the person locking matches the lock's owner, allow the lock to # happen: if [ "$LOCK_OWNER" == "$USER" ]; then exit 0 fi # Otherwise, we've got an owner mismatch, so return failure: echo "Error: $PATH already locked by ${LOCK_OWNER}." 1>&2 exit 1 svnroot/hooks/.#pre-revprop-change.tmpl.00000664000175000017500000000531310314466413020162 0ustar doudoudoudou#!/bin/sh # PRE-REVPROP-CHANGE HOOK # # The pre-revprop-change hook is invoked before a revision property # is added, modified or deleted. Subversion runs this hook by invoking # a program (script, executable, binary, etc.) named 'pre-revprop-change' # (for which this file is a template), with the following ordered # arguments: # # [1] REPOS-PATH (the path to this repository) # [2] REVISION (the revision being tweaked) # [3] USER (the username of the person tweaking the property) # [4] PROPNAME (the property being set on the revision) # [5] ACTION (the property is being 'A'dded, 'M'odified, or 'D'eleted) # # [STDIN] PROPVAL ** the new property value is passed via STDIN. # # If the hook program exits with success, the propchange happens; but # if it exits with failure (non-zero), the propchange doesn't happen. # The hook program can use the 'svnlook' utility to examine the # existing value of the revision property. # # WARNING: unlike other hooks, this hook MUST exist for revision # properties to be changed. If the hook does not exist, Subversion # will behave as if the hook were present, but failed. The reason # for this is that revision properties are UNVERSIONED, meaning that # a successful propchange is destructive; the old value is gone # forever. We recommend the hook back up the old value somewhere. # # On a Unix system, the normal procedure is to have 'pre-revprop-change' # invoke other programs to do the real work, though it may do the # work itself too. # # Note that 'pre-revprop-change' must be executable by the user(s) who will # invoke it (typically the user httpd runs as), and that user must # have filesystem-level permission to access the repository. # # On a Windows system, you should name the hook program # 'pre-revprop-change.bat' or 'pre-revprop-change.exe', # but the basic idea is the same. # # The hook program typically does not inherit the environment of # its parent process. For example, a common problem is for the # PATH environment variable to not be set to its usual value, so # that subprograms fail to launch unless invoked via absolute path. # If you're having unexpected problems with a hook program, the # culprit may be unusual (or missing) environment variables. # # Here is an example hook script, for a Unix /bin/sh interpreter.# For more examples and pre-written hooks, see those in # the Subversion repository at # http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and # http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/ REPOS="$1" REV="$2" USER="$3" PROPNAME="$4" ACTION="$5" if [ "$ACTION" = "M" -a "$PROPNAME" = "svn:log" ]; then exit 0; fi echo "Changing revision properties other than svn:log is prohibited" >&2 exit 1 svnroot/hooks/.#pre-unlock.tmpl.00000664000175000017500000000370410314466413016537 0ustar doudoudoudou#!/bin/sh # PRE-UNLOCK HOOK # # The pre-unlock hook is invoked before an exclusive lock is # destroyed. Subversion runs this hook by invoking a program # (script, executable, binary, etc.) named 'pre-unlock' (for which # this file is a template), with the following ordered arguments: # # [1] REPOS-PATH (the path to this repository) # [2] PATH (the path in the repository about to be unlocked) # [3] USER (the user destroying the lock) # # The default working directory for the invocation is undefined, so # the program should set one explicitly if it cares. # # If the hook program exits with success, the lock is destroyed; but # if it exits with failure (non-zero), the unlock action is aborted # and STDERR is returned to the client. # On a Unix system, the normal procedure is to have 'pre-unlock' # invoke other programs to do the real work, though it may do the # work itself too. # # Note that 'pre-unlock' must be executable by the user(s) who will # invoke it (typically the user httpd runs as), and that user must # have filesystem-level permission to access the repository. # # On a Windows system, you should name the hook program # 'pre-unlock.bat' or 'pre-unlock.exe', # but the basic idea is the same. # # Here is an example hook script, for a Unix /bin/sh interpreter: REPOS="$1" PATH="$2" USER="$3" # If a lock is owned by a different person, don't allow it be broken. # (Maybe this script could send email to the to the lock owner?) SVNLOOK=/usr/bin/svnlook GREP=/bin/grep SED=/bin/sed LOCK_OWNER=`$SVNLOOK lock "$REPOS" "$PATH" | \ $GREP '^Owner: ' | $SED 's/Owner: //'` # If we get no result from svnlook, there's no lock, return success: if [ "$LOCK_OWNER" == "" ]; then exit 0 fi # If the person unlocking matches the lock's owner, return success: if [ "$LOCK_OWNER" == "$USER" ]; then exit 0 fi # Otherwise, we've got an owner mismatch, so return failure: echo "Error: $PATH locked by ${LOCK_OWNER}." 1>&2 exit 1 svnroot/hooks/.#start-commit.tmpl.00000664000175000017500000000413010314466413017075 0ustar doudoudoudou#!/bin/sh # START-COMMIT HOOK # # The start-commit hook is invoked before a Subversion txn is created # in the process of doing a commit. Subversion runs this hook # by invoking a program (script, executable, binary, etc.) named # 'start-commit' (for which this file is a template) # with the following ordered arguments: # # [1] REPOS-PATH (the path to this repository) # [2] USER (the authenticated user attempting to commit) # # The default working directory for the invocation is undefined, so # the program should set one explicitly if it cares. # # If the hook program exits with success, the commit continues; but # if it exits with failure (non-zero), the commit is stopped before # a Subversion txn is created, and STDERR is returned to the client. # # On a Unix system, the normal procedure is to have 'start-commit' # invoke other programs to do the real work, though it may do the # work itself too. # # Note that 'start-commit' must be executable by the user(s) who will # invoke it (typically the user httpd runs as), and that user must # have filesystem-level permission to access the repository. # # On a Windows system, you should name the hook program # 'start-commit.bat' or 'start-commit.exe', # but the basic idea is the same. # # The hook program typically does not inherit the environment of # its parent process. For example, a common problem is for the # PATH environment variable to not be set to its usual value, so # that subprograms fail to launch unless invoked via absolute path. # If you're having unexpected problems with a hook program, the # culprit may be unusual (or missing) environment variables. # # Here is an example hook script, for a Unix /bin/sh interpreter.# For more examples and pre-written hooks, see those in # the Subversion repository at # http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and # http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/ REPOS="$1" USER="$2" commit-allower.pl --repository "$REPOS" --user "$USER" || exit 1 special-auth-check.py --user "$USER" --auth-level 3 || exit 1 # All checks passed, so allow the commit. exit 0 svnroot/conf/0000775000175000017500000000000010314766352013106 5ustar doudoudoudousvnroot/conf/svnserve.conf0000664000175000017500000000206610314466413015627 0ustar doudoudoudou### This file controls the configuration of the svnserve daemon, if you ### use it to allow access to this repository. (If you only allow ### access through http: and/or file: URLs, then this file is ### irrelevant.) ### Visit http://subversion.tigris.org/ for more information. # [general] ### These options control access to the repository for unauthenticated ### and authenticated users. Valid values are "write", "read", ### and "none". The sample settings below are the defaults. # anon-access = read # auth-access = write ### The password-db option controls the location of the password ### database file. Unless you specify a path starting with a /, ### the file's location is relative to the conf directory. ### Uncomment the line below to use the default password file. # password-db = passwd ### This option specifies the authentication realm of the repository. ### If two repositories have the same authentication realm, they should ### have the same password database, and vice versa. The default realm ### is repository's uuid. # realm = My First Repository svnroot/conf/passwd0000664000175000017500000000046710314466413014334 0ustar doudoudoudou### This file is an example password file for svnserve. ### Its format is similar to that of svnserve.conf. As shown in the ### example below it contains one section labelled [users]. ### The name and password for each user follow, one account per line. # [users] # harry = harryssecret # sally = sallyssecret svnroot/conf/CVS/0000775000175000017500000000000010314766033013535 5ustar doudoudoudousvnroot/conf/CVS/Root0000664000175000017500000000005610314765712014407 0ustar doudoudoudou:ext:lapinot@rubyforge.org:/var/cvs/autobuild svnroot/conf/CVS/Repository0000664000175000017500000000004110314765712015635 0ustar doudoudoudouautobuild/test/data/svnroot/conf svnroot/conf/CVS/Entries0000664000175000017500000000011110314766033015062 0ustar doudoudoudouD/CVS//// /passwd/0/dummy timestamp// /svnserve.conf/0/dummy timestamp// svnroot/conf/CVS/CVS/0000775000175000017500000000000010314766033014170 5ustar doudoudoudousvnroot/conf/CVS/CVS/Root0000664000175000017500000000005610314766033015037 0ustar doudoudoudou:ext:lapinot@rubyforge.org:/var/cvs/autobuild svnroot/conf/CVS/CVS/Repository0000664000175000017500000000004510314766033016271 0ustar doudoudoudouautobuild/test/data/svnroot/conf/CVS svnroot/conf/CVS/CVS/Entries0000664000175000017500000000000210314766033015514 0ustar doudoudoudouD svnroot/conf/.#passwd.00000664000175000017500000000046710314466413014613 0ustar doudoudoudou### This file is an example password file for svnserve. ### Its format is similar to that of svnserve.conf. As shown in the ### example below it contains one section labelled [users]. ### The name and password for each user follow, one account per line. # [users] # harry = harryssecret # sally = sallyssecret svnroot/conf/.#svnserve.conf.00000664000175000017500000000206610314466413016106 0ustar doudoudoudou### This file controls the configuration of the svnserve daemon, if you ### use it to allow access to this repository. (If you only allow ### access through http: and/or file: URLs, then this file is ### irrelevant.) ### Visit http://subversion.tigris.org/ for more information. # [general] ### These options control access to the repository for unauthenticated ### and authenticated users. Valid values are "write", "read", ### and "none". The sample settings below are the defaults. # anon-access = read # auth-access = write ### The password-db option controls the location of the password ### database file. Unless you specify a path starting with a /, ### the file's location is relative to the conf directory. ### Uncomment the line below to use the default password file. # password-db = passwd ### This option specifies the authentication realm of the repository. ### If two repositories have the same authentication realm, they should ### have the same password database, and vice versa. The default realm ### is repository's uuid. # realm = My First Repository svnroot/README.txt0000664000175000017500000000057310314466413013657 0ustar doudoudoudouThis is a Subversion repository; use the 'svnadmin' tool to examine it. Do not add, delete, or modify files here unless you know how to avoid corrupting the repository. If the directory "db" contains a Berkeley DB environment, you may need to tweak the values in "db/DB_CONFIG" to match the requirements of your site. Visit http://subversion.tigris.org/ for more information. svnroot/db/0002775000175000017500000000000010314766354012552 5ustar doudoudoudousvnroot/db/fs-type0000664000175000017500000000000510314466413014046 0ustar doudoudoudoufsfs svnroot/db/revs/0002775000175000017500000000000010314766353013530 5ustar doudoudoudousvnroot/db/revs/00000664000175000017500000000016310314466413013602 0ustar doudoudoudouPLAIN END ENDREP id: 0.0.r0/17 type: dir count: 0 text: 0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e cpath: / 17 107 svnroot/db/revs/10000664000175000017500000000104610314466471013610 0ustar doudoudoudouDELTA SVNˆFoo Bar ENDREP id: 2.0.r1/31 type: file count: 0 text: 1 0 18 8 ce51b3533fab153125282199313e6118 cpath: /svn/test copyroot: 0 / PLAIN K 4 test V 14 file 2.0.r1/31 END ENDREP id: 1.0.r1/191 type: dir count: 0 text: 1 145 33 33 197acd12ad1ce54dde2cc59f97dfb2c8 cpath: /svn copyroot: 0 / PLAIN K 3 svn V 14 dir 1.0.r1/191 END ENDREP id: 0.0.r1/348 type: dir pred: 0.0.r0/17 count: 1 text: 1 303 32 32 46d8a2c7a1bea77a75647d6a02985e91 cpath: / copyroot: 0 / _1.0.t0-1 add true false /svn/test _0.0.t0-1 add false false /svn 348 473 svnroot/db/revs/CVS/0002775000175000017500000000000010314766100014151 5ustar doudoudoudousvnroot/db/revs/CVS/Root0000664000175000017500000000005610314766033015023 0ustar doudoudoudou:ext:lapinot@rubyforge.org:/var/cvs/autobuild svnroot/db/revs/CVS/Repository0000664000175000017500000000004410314766033016254 0ustar doudoudoudouautobuild/test/data/svnroot/db/revs svnroot/db/revs/CVS/Entries0000664000175000017500000000007010314766100015500 0ustar doudoudoudouD/CVS//// /0/0/dummy timestamp// /1/0/dummy timestamp// svnroot/db/revs/CVS/CVS/0002775000175000017500000000000010314766100014604 5ustar doudoudoudousvnroot/db/revs/CVS/CVS/Root0000664000175000017500000000005610314766100015451 0ustar doudoudoudou:ext:lapinot@rubyforge.org:/var/cvs/autobuild svnroot/db/revs/CVS/CVS/Repository0000664000175000017500000000005010314766100016677 0ustar doudoudoudouautobuild/test/data/svnroot/db/revs/CVS svnroot/db/revs/CVS/CVS/Entries0000664000175000017500000000000210314766100016126 0ustar doudoudoudouD svnroot/db/revs/.#0.00000664000175000017500000000016310314466413014061 0ustar doudoudoudouPLAIN END ENDREP id: 0.0.r0/17 type: dir count: 0 text: 0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e cpath: / 17 107 svnroot/db/revs/.#1.00000664000175000017500000000104610314466471014067 0ustar doudoudoudouDELTA SVNˆFoo Bar ENDREP id: 2.0.r1/31 type: file count: 0 text: 1 0 18 8 ce51b3533fab153125282199313e6118 cpath: /svn/test copyroot: 0 / PLAIN K 4 test V 14 file 2.0.r1/31 END ENDREP id: 1.0.r1/191 type: dir count: 0 text: 1 145 33 33 197acd12ad1ce54dde2cc59f97dfb2c8 cpath: /svn copyroot: 0 / PLAIN K 3 svn V 14 dir 1.0.r1/191 END ENDREP id: 0.0.r1/348 type: dir pred: 0.0.r0/17 count: 1 text: 1 303 32 32 46d8a2c7a1bea77a75647d6a02985e91 cpath: / copyroot: 0 / _1.0.t0-1 add true false /svn/test _0.0.t0-1 add false false /svn 348 473 svnroot/db/revprops/0002775000175000017500000000000010314766353014431 5ustar doudoudoudousvnroot/db/revprops/10000664000175000017500000000013610314466471014510 0ustar doudoudoudouK 10 svn:author V 6 doudou K 8 svn:date V 27 2005-09-22T08:37:13.289329Z K 7 svn:log V 0 END svnroot/db/revprops/00000664000175000017500000000006210314466413014501 0ustar doudoudoudouK 8 svn:date V 27 2005-09-22T08:36:27.785050Z END svnroot/db/revprops/CVS/0002775000175000017500000000000010314766100015052 5ustar doudoudoudousvnroot/db/revprops/CVS/Root0000664000175000017500000000005610314766033015724 0ustar doudoudoudou:ext:lapinot@rubyforge.org:/var/cvs/autobuild svnroot/db/revprops/CVS/Repository0000664000175000017500000000005010314766033017152 0ustar doudoudoudouautobuild/test/data/svnroot/db/revprops svnroot/db/revprops/CVS/Entries0000664000175000017500000000007010314766100016401 0ustar doudoudoudouD/CVS//// /0/0/dummy timestamp// /1/0/dummy timestamp// svnroot/db/revprops/CVS/CVS/0002775000175000017500000000000010314766100015505 5ustar doudoudoudousvnroot/db/revprops/CVS/CVS/Root0000664000175000017500000000005610314766100016352 0ustar doudoudoudou:ext:lapinot@rubyforge.org:/var/cvs/autobuild svnroot/db/revprops/CVS/CVS/Repository0000664000175000017500000000005410314766100017604 0ustar doudoudoudouautobuild/test/data/svnroot/db/revprops/CVS svnroot/db/revprops/CVS/CVS/Entries0000664000175000017500000000000210314766100017027 0ustar doudoudoudouD svnroot/db/revprops/.#0.00000664000175000017500000000006210314466413014760 0ustar doudoudoudouK 8 svn:date V 27 2005-09-22T08:36:27.785050Z END svnroot/db/revprops/.#1.00000664000175000017500000000013610314466471014767 0ustar doudoudoudouK 10 svn:author V 6 doudou K 8 svn:date V 27 2005-09-22T08:37:13.289329Z K 7 svn:log V 0 END svnroot/db/current0000664000175000017500000000000610314466471014146 0ustar doudoudoudou1 3 1 svnroot/db/write-lock0000664000175000017500000000000010314466413014532 0ustar doudoudoudousvnroot/db/uuid0000664000175000017500000000004510314466413013431 0ustar doudoudoudoua1106930-5801-0410-a3fb-ec1355edff87 svnroot/db/CVS/0002775000175000017500000000000010314766354013205 5ustar doudoudoudousvnroot/db/CVS/Root0000664000175000017500000000005610314765713014050 0ustar doudoudoudou:ext:lapinot@rubyforge.org:/var/cvs/autobuild svnroot/db/CVS/Repository0000644000175000017500000000003710314765713015301 0ustar doudoudoudouautobuild/test/data/svnroot/db svnroot/db/CVS/Entries0000644000175000017500000000030710314766033014527 0ustar doudoudoudouD/CVS//// D/revprops//// D/revs//// D/transactions//// /current/0/dummy timestamp// /format/0/dummy timestamp// /fs-type/0/dummy timestamp// /uuid/0/dummy timestamp// /write-lock/0/dummy timestamp// svnroot/db/CVS/CVS/0002775000175000017500000000000010314766100013625 5ustar doudoudoudousvnroot/db/CVS/CVS/Root0000664000175000017500000000005610314766033014477 0ustar doudoudoudou:ext:lapinot@rubyforge.org:/var/cvs/autobuild svnroot/db/CVS/CVS/Repository0000664000175000017500000000004310314766033015727 0ustar doudoudoudouautobuild/test/data/svnroot/db/CVS svnroot/db/CVS/CVS/Entries0000664000175000017500000000014110314766100015153 0ustar doudoudoudouD/CVS//// /Entries/0/dummy timestamp// /Repository/0/dummy timestamp// /Root/0/dummy timestamp// svnroot/db/CVS/CVS/CVS/0002775000175000017500000000000010314766100014260 5ustar doudoudoudousvnroot/db/CVS/CVS/CVS/Root0000664000175000017500000000005610314766100015125 0ustar doudoudoudou:ext:lapinot@rubyforge.org:/var/cvs/autobuild svnroot/db/CVS/CVS/CVS/Repository0000664000175000017500000000004710314766100016361 0ustar doudoudoudouautobuild/test/data/svnroot/db/CVS/CVS svnroot/db/CVS/CVS/CVS/Entries0000664000175000017500000000000210314766100015602 0ustar doudoudoudouD svnroot/db/CVS/Entries.Log0000664000175000017500000000002510314766354015254 0ustar doudoudoudouR D/transactions//// svnroot/db/format0000444000175000017500000000000210314466413013740 0ustar doudoudoudou1 svnroot/db/.#current.00000664000175000017500000000000610314466471014425 0ustar doudoudoudou1 3 1 svnroot/db/.#format.00000444000175000017500000000000210314466413014217 0ustar doudoudoudou1 svnroot/db/.#fs-type.00000664000175000017500000000000510314466413014325 0ustar doudoudoudoufsfs svnroot/db/.#uuid.00000664000175000017500000000004510314466413013710 0ustar doudoudoudoua1106930-5801-0410-a3fb-ec1355edff87 svnroot/db/.#write-lock.00000664000175000017500000000000010314466413015011 0ustar doudoudoudousvnroot/format0000444000175000017500000000000210314466413013353 0ustar doudoudoudou3 svnroot/CVS/0000775000175000017500000000000010314766354012616 5ustar doudoudoudousvnroot/CVS/Root0000664000175000017500000000005610314765613013462 0ustar doudoudoudou:ext:lapinot@rubyforge.org:/var/cvs/autobuild svnroot/CVS/Repository0000644000175000017500000000003410314765613014710 0ustar doudoudoudouautobuild/test/data/svnroot svnroot/CVS/Entries0000644000175000017500000000017410314765713014150 0ustar doudoudoudouD/conf//// D/CVS//// D/dav//// D/db//// D/hooks//// D/locks//// /format/0/dummy timestamp// /README.txt/0/dummy timestamp// svnroot/CVS/Entries.Log0000664000175000017500000000001410314766354014665 0ustar doudoudoudouR D/dav//// svnroot/CVS/CVS/0000775000175000017500000000000010314766033013243 5ustar doudoudoudousvnroot/CVS/CVS/Root0000664000175000017500000000005610314765713014116 0ustar doudoudoudou:ext:lapinot@rubyforge.org:/var/cvs/autobuild svnroot/CVS/CVS/Repository0000664000175000017500000000004010314765713015343 0ustar doudoudoudouautobuild/test/data/svnroot/CVS svnroot/CVS/CVS/Entries0000664000175000017500000000014110314766033014573 0ustar doudoudoudouD/CVS//// /Entries/0/dummy timestamp// /Repository/0/dummy timestamp// /Root/0/dummy timestamp// svnroot/CVS/CVS/CVS/0000775000175000017500000000000010314766033013676 5ustar doudoudoudousvnroot/CVS/CVS/CVS/Root0000664000175000017500000000005610314766033014545 0ustar doudoudoudou:ext:lapinot@rubyforge.org:/var/cvs/autobuild svnroot/CVS/CVS/CVS/Repository0000664000175000017500000000004410314766033015776 0ustar doudoudoudouautobuild/test/data/svnroot/CVS/CVS svnroot/CVS/CVS/CVS/Entries0000664000175000017500000000000210314766033015222 0ustar doudoudoudouD svnroot/.#README.txt.00000664000175000017500000000057310314466413014136 0ustar doudoudoudouThis is a Subversion repository; use the 'svnadmin' tool to examine it. Do not add, delete, or modify files here unless you know how to avoid corrupting the repository. If the directory "db" contains a Berkeley DB environment, you may need to tweak the values in "db/DB_CONFIG" to match the requirements of your site. Visit http://subversion.tigris.org/ for more information. svnroot/.#format.00000444000175000017500000000000210314466413013632 0ustar doudoudoudou3