[SPIP Zone] [Spip-zone-commit] r26717 - // /conf/ /db/ /db/revprops/ /db/revprops/0/ /db/revs/ /db/revs/0/ /db/transactions/ /db/txn-protorevs/ /hooks/ /locks/

ouh là là ! t’as du mal à commiter toi !

2009/2/17 <olivier.gautier@ac-rouen.fr>

Author: olivier.gautier@ac-rouen.fr
Date: Tue Feb 17 23:45:30 2009
New Revision: 26717

Log: (empty)

Added:
README.txt
conf/
conf/authz
conf/passwd
conf/svnserve.conf
db/
db/current
db/format
db/fs-type
db/revprops/
db/revprops/0/
db/revprops/0/0
db/revs/
db/revs/0/
db/revs/0/0
db/transactions/
db/txn-current
db/txn-current-lock
db/txn-protorevs/
db/uuid
db/write-lock
format
hooks/
hooks/post-commit.tmpl
hooks/post-lock.tmpl
hooks/post-revprop-change.tmpl
hooks/post-unlock.tmpl
hooks/pre-commit.tmpl
hooks/pre-lock.tmpl
hooks/pre-revprop-change.tmpl
hooks/pre-unlock.tmpl
hooks/start-commit.tmpl
locks/
locks/db-logs.lock
locks/db.lock

Added: README.txt

— README.txt (added)
+++ README.txt Tue Feb 17 23:45:30 2009
@@ -0,0 +1,5 @@
+This 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.
+
+Visit http://subversion.tigris.org/ for more information.

Added: conf/authz

— conf/authz (added)
+++ conf/authz Tue Feb 17 23:45:30 2009
@@ -0,0 +1,32 @@
+### This file is an example authorization file for svnserve.
+### Its format is identical to that of mod_authz_svn authorization
+### files.
+### As shown below each section defines authorizations for the path and
+### (optional) repository specified by the section name.
+### The authorizations follow. An authorization line can refer to:
+### - a single user,
+### - a group of users defined in a special [groups] section,
+### - an alias defined in a special [aliases] section,
+### - all authenticated users, using the ‹ $authenticated › token,
+### - only anonymous users, using the ‹ $anonymous › token,
+### - anyone, using the ‹ * › wildcard.
+###
+### A match can be inverted by prefixing the rule with ‹ ~ ›. Rules can
+### grant read (‹ r ›) access, read-write (‹ rw ›) access, or no access
+### (‹  ›).
+
+[aliases]
+# joe = /C=XZ/ST=Dessert/L=Snake City/O=Snake Oil, Ltd./OU=Research Institute/CN=Joe Average
+
+[groups]
+# harry_and_sally = harry,sally
+# harry_sally_and_joe = harry,sally,&joe
+
+# [/foo/bar]
+# harry = rw
+# &joe = r
+# * =
+
+# [repository:/baz/fuz]
+# @harry_and_sally = rw
+# * = r

Added: conf/passwd

— conf/passwd (added)
+++ conf/passwd Tue Feb 17 23:45:30 2009
@@ -0,0 +1,8 @@
+### 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

Added: conf/svnserve.conf

— conf/svnserve.conf (added)
+++ conf/svnserve.conf Tue Feb 17 23:45:30 2009
@@ -0,0 +1,47 @@
+### 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 directory containing
+### this configuration file.
+### If SASL is enabled (see below), this file will NOT be used.
+### Uncomment the line below to use the default password file.
+# password-db = passwd
+### The authz-db option controls the location of the authorization
+### rules for path-based access control. Unless you specify a path
+### starting with a /, the file’s location is relative to the the
+### directory containing this file. If you don’t specify an
+### authz-db, no path-based access control is done.
+### Uncomment the line below to use the default authorization file.
+# authz-db = authz
+### 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
+
+[sasl]
+### This option specifies whether you want to use the Cyrus SASL
+### library for authentication. Default is false.
+### This section will be ignored if svnserve is not built with Cyrus
+### SASL support; to check, run ‹ svnserve --version › and look for a line
+### reading ‹ Cyrus SASL authentication is available. ›
+# use-sasl = true
+### These options specify the desired strength of the security layer
+### that you want SASL to provide. 0 means no encryption, 1 means
+### integrity-checking only, values larger than 1 are correlated
+### to the effective key length for encryption (e.g. 128 means 128-bit
+### encryption). The values below are the defaults.
+# min-encryption = 0
+# max-encryption = 256

Added: db/current

— db/current (added)
+++ db/current Tue Feb 17 23:45:30 2009
@@ -0,0 +1 @@
+0

Added: db/format

— db/format (added)
+++ db/format Tue Feb 17 23:45:30 2009
@@ -0,0 +1,2 @@
+3
+layout sharded 1000

Added: db/fs-type

— db/fs-type (added)
+++ db/fs-type Tue Feb 17 23:45:30 2009
@@ -0,0 +1 @@
+fsfs

Added: db/revprops/0/0

— db/revprops/0/0 (added)
+++ db/revprops/0/0 Tue Feb 17 23:45:30 2009
@@ -0,0 +1,5 @@
+K 8
+svn:date
+V 27
+2009-02-17T22:40:18.892440Z
+END

Added: db/revs/0/0

— db/revs/0/0 (added)
+++ db/revs/0/0 Tue Feb 17 23:45:30 2009
@@ -0,0 +1,11 @@
+PLAIN
+END
+ENDREP
+id: 0.0.r0/17
+type: dir
+count: 0
+text: 0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e
+cpath: /
+
+
+17 107

Added: db/txn-current

— db/txn-current (added)
+++ db/txn-current Tue Feb 17 23:45:30 2009
@@ -0,0 +1 @@
+0

Added: db/txn-current-lock

(empty)

Added: db/uuid

— db/uuid (added)
+++ db/uuid Tue Feb 17 23:45:30 2009
@@ -0,0 +1 @@
+7dd5b84f-0b72-da4c-b591-2bead95e7804

Added: db/write-lock

(empty)

Added: format

— format (added)
+++ format Tue Feb 17 23:45:30 2009
@@ -0,0 +1 @@
+5

Added: hooks/post-commit.tmpl

— hooks/post-commit.tmpl (added)
+++ hooks/post-commit.tmpl Tue Feb 17 23:45:30 2009
@@ -0,0 +1,51 @@
+#!/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 »
+
+commit-email.pl « $REPOS » « $REV » commit-watchers@example.org
+log-commit.py --repository « $REPOS » --revision « $REV »

Added: hooks/post-lock.tmpl

— hooks/post-lock.tmpl (added)

[… 531 lines stripped …]


Spip-zone-commit@rezo.net - http://listes.rezo.net/mailman/listinfo/spip-zone-commit

PRIGENT Yohann

Yohann Prigent a écrit :

ouh là là ! t'as du mal à commiter toi !

Heu... je n'ai rien commité du tout.

Voilà mes premiers tests sous Vista et Tortoize, ce qui me donne ce truc...
Vraiment désolé : si quelqu'un peut réparer car je crains de faire pire que mieux...

Bonne soirée.

2009/2/17 <olivier.gautier@ac-rouen.fr <mailto:olivier.gautier@ac-rouen.fr>>

    Author: olivier.gautier@ac-rouen.fr
    <mailto:olivier.gautier@ac-rouen.fr>
    Date: Tue Feb 17 23:45:30 2009
    New Revision: 26717

    Log: (empty)

    Added:
       README.txt
       conf/
       conf/authz
       conf/passwd
       conf/svnserve.conf
       db/
       db/current
       db/format
       db/fs-type
       db/revprops/
       db/revprops/0/
       db/revprops/0/0
       db/revs/
       db/revs/0/
       db/revs/0/0
       db/transactions/
       db/txn-current
       db/txn-current-lock
       db/txn-protorevs/
       db/uuid
       db/write-lock
       format
       hooks/
       hooks/post-commit.tmpl
       hooks/post-lock.tmpl
       hooks/post-revprop-change.tmpl
       hooks/post-unlock.tmpl
       hooks/pre-commit.tmpl
       hooks/pre-lock.tmpl
       hooks/pre-revprop-change.tmpl
       hooks/pre-unlock.tmpl
       hooks/start-commit.tmpl
       locks/
       locks/db-logs.lock
       locks/db.lock

    Added: README.txt
    ==============================================================================
    --- README.txt (added)
    +++ README.txt Tue Feb 17 23:45:30 2009
    @@ -0,0 +1,5 @@
    +This 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.
    +
    +Visit http://subversion.tigris.org/ for more information.

    Added: conf/authz
    ==============================================================================
    --- conf/authz (added)
    +++ conf/authz Tue Feb 17 23:45:30 2009
    @@ -0,0 +1,32 @@
    +### This file is an example authorization file for svnserve.
    +### Its format is identical to that of mod_authz_svn authorization
    +### files.
    +### As shown below each section defines authorizations for the
    path and
    +### (optional) repository specified by the section name.
    +### The authorizations follow. An authorization line can refer to:
    +### - a single user,
    +### - a group of users defined in a special [groups] section,
    +### - an alias defined in a special [aliases] section,
    +### - all authenticated users, using the '$authenticated' token,
    +### - only anonymous users, using the '$anonymous' token,
    +### - anyone, using the '*' wildcard.
    +###
    +### A match can be inverted by prefixing the rule with '~'. Rules can
    +### grant read ('r') access, read-write ('rw') access, or no access
    +### ('').
    +
    +[aliases]
    +# joe = /C=XZ/ST=Dessert/L=Snake City/O=Snake Oil,
    Ltd./OU=Research Institute/CN=Joe Average
    +
    +[groups]
    +# harry_and_sally = harry,sally
    +# harry_sally_and_joe = harry,sally,&joe
    +
    +# [/foo/bar]
    +# harry = rw
    +# &joe = r
    +# * =
    +
    +# [repository:/baz/fuz]
    +# @harry_and_sally = rw
    +# * = r

    Added: conf/passwd
    ==============================================================================
    --- conf/passwd (added)
    +++ conf/passwd Tue Feb 17 23:45:30 2009
    @@ -0,0 +1,8 @@
    +### 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

    Added: conf/svnserve.conf
    ==============================================================================
    --- conf/svnserve.conf (added)
    +++ conf/svnserve.conf Tue Feb 17 23:45:30 2009
    @@ -0,0 +1,47 @@
    +### 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 directory containing
    +### this configuration file.
    +### If SASL is enabled (see below), this file will NOT be used.
    +### Uncomment the line below to use the default password file.
    +# password-db = passwd
    +### The authz-db option controls the location of the authorization
    +### rules for path-based access control. Unless you specify a path
    +### starting with a /, the file's location is relative to the the
    +### directory containing this file. If you don't specify an
    +### authz-db, no path-based access control is done.
    +### Uncomment the line below to use the default authorization file.
    +# authz-db = authz
    +### 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
    +
    +[sasl]
    +### This option specifies whether you want to use the Cyrus SASL
    +### library for authentication. Default is false.
    +### This section will be ignored if svnserve is not built with Cyrus
    +### SASL support; to check, run 'svnserve --version' and look for
    a line
    +### reading 'Cyrus SASL authentication is available.'
    +# use-sasl = true
    +### These options specify the desired strength of the security layer
    +### that you want SASL to provide. 0 means no encryption, 1 means
    +### integrity-checking only, values larger than 1 are correlated
    +### to the effective key length for encryption (e.g. 128 means
    128-bit
    +### encryption). The values below are the defaults.
    +# min-encryption = 0
    +# max-encryption = 256

    Added: db/current
    ==============================================================================
    --- db/current (added)
    +++ db/current Tue Feb 17 23:45:30 2009
    @@ -0,0 +1 @@
    +0

    Added: db/format
    ==============================================================================
    --- db/format (added)
    +++ db/format Tue Feb 17 23:45:30 2009
    @@ -0,0 +1,2 @@
    +3
    +layout sharded 1000

    Added: db/fs-type
    ==============================================================================
    --- db/fs-type (added)
    +++ db/fs-type Tue Feb 17 23:45:30 2009
    @@ -0,0 +1 @@
    +fsfs

    Added: db/revprops/0/0
    ==============================================================================
    --- db/revprops/0/0 (added)
    +++ db/revprops/0/0 Tue Feb 17 23:45:30 2009
    @@ -0,0 +1,5 @@
    +K 8
    +svn:date
    +V 27
    +2009-02-17T22:40:18.892440Z
    +END

    Added: db/revs/0/0
    ==============================================================================
    --- db/revs/0/0 (added)
    +++ db/revs/0/0 Tue Feb 17 23:45:30 2009
    @@ -0,0 +1,11 @@
    +PLAIN
    +END
    +ENDREP
    +id: 0.0.r0/17
    +type: dir
    +count: 0
    +text: 0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e
    +cpath: /
    +
    +17 107

    Added: db/txn-current
    ==============================================================================
    --- db/txn-current (added)
    +++ db/txn-current Tue Feb 17 23:45:30 2009
    @@ -0,0 +1 @@
    +0

    Added: db/txn-current-lock
    ==============================================================================
       (empty)

    Added: db/uuid
    ==============================================================================
    --- db/uuid (added)
    +++ db/uuid Tue Feb 17 23:45:30 2009
    @@ -0,0 +1 @@
    +7dd5b84f-0b72-da4c-b591-2bead95e7804

    Added: db/write-lock
    ==============================================================================
       (empty)

    Added: format
    ==============================================================================
    --- format (added)
    +++ format Tue Feb 17 23:45:30 2009
    @@ -0,0 +1 @@
    +5

    Added: hooks/post-commit.tmpl
    ==============================================================================
    --- hooks/post-commit.tmpl (added)
    +++ hooks/post-commit.tmpl Tue Feb 17 23:45:30 2009
    @@ -0,0 +1,51 @@
    +#!/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"
    +
    +commit-email.pl "$REPOS" "$REV" commit-watchers@example.org
    <mailto:commit-watchers@example.org>
    +log-commit.py --repository "$REPOS" --revision "$REV"

    Added: hooks/post-lock.tmpl
    ==============================================================================
    --- hooks/post-lock.tmpl (added)

    [... 531 lines stripped ...]
    _______________________________________________
    Spip-zone-commit@rezo.net <mailto:Spip-zone-commit@rezo.net> -
    http://listes.rezo.net/mailman/listinfo/spip-zone-commit

--

PRIGENT Yohann
------------------------------------------------------------------------

_______________________________________________
Spip-zone-commit@rezo.net - http://listes.rezo.net/mailman/listinfo/spip-zone-commit
  

lol Vista faut pas prendre :stuck_out_tongue: !
Je vais essayer de réparer

a+

Le 17 février 2009 23:58, Olivier Gautier <olivier.gautier@ac-rouen.fr> a écrit :

Yohann Prigent a écrit :

ouh là là ! t’as du mal à commiter toi !

Heu… je n’ai rien commité du tout.

Voilà mes premiers tests sous Vista et Tortoize, ce qui me donne ce truc…
Vraiment désolé : si quelqu’un peut réparer car je crains de faire pire que mieux…

Bonne soirée.

2009/2/17 <olivier.gautier@ac-rouen.fr mailto:[olivier.gautier@ac-rouen.fr](mailto:olivier.gautier@ac-rouen.fr)>

Author: olivier.gautier@ac-rouen.fr
mailto:[olivier.gautier@ac-rouen.fr](mailto:olivier.gautier@ac-rouen.fr)
Date: Tue Feb 17 23:45:30 2009
New Revision: 26717

Log: (empty)

Added:
README.txt
conf/
conf/authz
conf/passwd
conf/svnserve.conf
db/
db/current
db/format
db/fs-type
db/revprops/
db/revprops/0/
db/revprops/0/0
db/revs/
db/revs/0/
db/revs/0/0
db/transactions/
db/txn-current
db/txn-current-lock
db/txn-protorevs/
db/uuid
db/write-lock
format
hooks/
hooks/post-commit.tmpl
hooks/post-lock.tmpl
hooks/post-revprop-change.tmpl
hooks/post-unlock.tmpl
hooks/pre-commit.tmpl
hooks/pre-lock.tmpl
hooks/pre-revprop-change.tmpl
hooks/pre-unlock.tmpl
hooks/start-commit.tmpl
locks/
locks/db-logs.lock
locks/db.lock

Added: README.txt

— README.txt (added)
+++ README.txt Tue Feb 17 23:45:30 2009
@@ -0,0 +1,5 @@
+This 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.
+
+Visit http://subversion.tigris.org/ for more information.

Added: conf/authz

— conf/authz (added)
+++ conf/authz Tue Feb 17 23:45:30 2009
@@ -0,0 +1,32 @@
+### This file is an example authorization file for svnserve.
+### Its format is identical to that of mod_authz_svn authorization
+### files.
+### As shown below each section defines authorizations for the
path and
+### (optional) repository specified by the section name.
+### The authorizations follow. An authorization line can refer to:
+### - a single user,
+### - a group of users defined in a special [groups] section,
+### - an alias defined in a special [aliases] section,
+### - all authenticated users, using the ‹ $authenticated › token,
+### - only anonymous users, using the ‹ $anonymous › token,
+### - anyone, using the ‹ * › wildcard.
+###
+### A match can be inverted by prefixing the rule with ‹ ~ ›. Rules can
+### grant read (‹ r ›) access, read-write (‹ rw ›) access, or no access
+### (‹  ›).
+
+[aliases]
+# joe = /C=XZ/ST=Dessert/L=Snake City/O=Snake Oil,
Ltd./OU=Research Institute/CN=Joe Average
+
+[groups]
+# harry_and_sally = harry,sally
+# harry_sally_and_joe = harry,sally,&joe
+
+# [/foo/bar]
+# harry = rw
+# &joe = r
+# * =
+
+# [repository:/baz/fuz]
+# @harry_and_sally = rw
+# * = r

Added: conf/passwd

— conf/passwd (added)
+++ conf/passwd Tue Feb 17 23:45:30 2009
@@ -0,0 +1,8 @@
+### 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

Added: conf/svnserve.conf

— conf/svnserve.conf (added)
+++ conf/svnserve.conf Tue Feb 17 23:45:30 2009
@@ -0,0 +1,47 @@
+### 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 directory containing
+### this configuration file.
+### If SASL is enabled (see below), this file will NOT be used.
+### Uncomment the line below to use the default password file.
+# password-db = passwd
+### The authz-db option controls the location of the authorization
+### rules for path-based access control. Unless you specify a path
+### starting with a /, the file’s location is relative to the the
+### directory containing this file. If you don’t specify an
+### authz-db, no path-based access control is done.
+### Uncomment the line below to use the default authorization file.
+# authz-db = authz
+### 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
+
+[sasl]
+### This option specifies whether you want to use the Cyrus SASL
+### library for authentication. Default is false.
+### This section will be ignored if svnserve is not built with Cyrus
+### SASL support; to check, run ‹ svnserve --version › and look for
a line
+### reading ‹ Cyrus SASL authentication is available. ›
+# use-sasl = true
+### These options specify the desired strength of the security layer
+### that you want SASL to provide. 0 means no encryption, 1 means
+### integrity-checking only, values larger than 1 are correlated
+### to the effective key length for encryption (e.g. 128 means
128-bit
+### encryption). The values below are the defaults.
+# min-encryption = 0
+# max-encryption = 256

Added: db/current

— db/current (added)
+++ db/current Tue Feb 17 23:45:30 2009
@@ -0,0 +1 @@
+0

Added: db/format

— db/format (added)
+++ db/format Tue Feb 17 23:45:30 2009
@@ -0,0 +1,2 @@
+3
+layout sharded 1000

Added: db/fs-type

— db/fs-type (added)
+++ db/fs-type Tue Feb 17 23:45:30 2009
@@ -0,0 +1 @@
+fsfs

Added: db/revprops/0/0

— db/revprops/0/0 (added)
+++ db/revprops/0/0 Tue Feb 17 23:45:30 2009
@@ -0,0 +1,5 @@
+K 8
+svn:date
+V 27
+2009-02-17T22:40:18.892440Z
+END

Added: db/revs/0/0

— db/revs/0/0 (added)
+++ db/revs/0/0 Tue Feb 17 23:45:30 2009
@@ -0,0 +1,11 @@
+PLAIN
+END
+ENDREP
+id: 0.0.r0/17
+type: dir
+count: 0
+text: 0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e
+cpath: /
+
+
+17 107

Added: db/txn-current

— db/txn-current (added)
+++ db/txn-current Tue Feb 17 23:45:30 2009
@@ -0,0 +1 @@
+0

Added: db/txn-current-lock

(empty)

Added: db/uuid

— db/uuid (added)
+++ db/uuid Tue Feb 17 23:45:30 2009
@@ -0,0 +1 @@
+7dd5b84f-0b72-da4c-b591-2bead95e7804

Added: db/write-lock

(empty)

Added: format

— format (added)
+++ format Tue Feb 17 23:45:30 2009
@@ -0,0 +1 @@
+5

Added: hooks/post-commit.tmpl

— hooks/post-commit.tmpl (added)
+++ hooks/post-commit.tmpl Tue Feb 17 23:45:30 2009
@@ -0,0 +1,51 @@
+#!/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 »
+
+commit-email.pl « $REPOS » « $REV » commit-watchers@example.org
mailto:[commit-watchers@example.org](mailto:commit-watchers@example.org)
+log-commit.py --repository « $REPOS » --revision « $REV »

Added: hooks/post-lock.tmpl

— hooks/post-lock.tmpl (added)

[… 531 lines stripped …]


Spip-zone-commit@rezo.net mailto:[Spip-zone-commit@rezo.net](mailto:Spip-zone-commit@rezo.net) -
http://listes.rezo.net/mailman/listinfo/spip-zone-commit

PRIGENT Yohann


Spip-zone-commit@rezo.net - http://listes.rezo.net/mailman/listinfo/spip-zone-commit


spip-zone@rezo.net - http://listes.rezo.net/mailman/listinfo/spip-zone

PRIGENT Yohann

Yohann Prigent a écrit :

lol Vista faut pas prendre :stuck_out_tongue: !
Je vais essayer de réparer

T'a oublié le readme Olivier dans le nettoyage.
Bonne soirée.

--
MM.

Matthieu Marcillaud a écrit :

Yohann Prigent a écrit :

lol Vista faut pas prendre :stuck_out_tongue: !

Je vois ça... pas terrible pour mes premiers tests sous Vista...

Je vais essayer de réparer

T'a oublié le readme Olivier dans le nettoyage.

J'ai effectivement vu ça mais la zone n'est plus joignable...
Je verrai cela demain.

Bonne soirée.

Bonne soirée à toi.

T'a oublié le readme Olivier dans le nettoyage.

readme et format, je viens de les supprimer

-- Fil

Fil a écrit :

T'a oublié le readme Olivier dans le nettoyage.
      
readme et format, je viens de les supprimer
  
Grand merci Fil.

Et encore désolé pour cette pagaille : saleté de Vista qui m'a joué un drôle de tour...

Bonne journée

-- Fil