On Jun 13, 2007, at 05:56, Giulio Troccoli wrote:
> I have been using Subversion for a year or so now and I have 3
> productions repositories and 3 or 4 testing repositories. I am
> using one
> of these repositories to test some scripts I am writing.
>
> My testing repository is a copy of a production one and what I did is:
> - svnadmin dump
> - create the repository dir
> - svnadmin create
> - svnadmin load
> - copy the hooks from production to testing
>
> The post-commit hook contains some code to change the log message,
> using
> svn ps, and it works fine in production. However it does not in
> testing.
> If I run the script manually svn stops when changing the svn:log
> property to ask for the Subversion password. I thought this was
> fine the
> first time, as it was a new repository, but even after I entered the
> password the first time (and it was the correct password as svn ps
> succeeded) this is not stored and I have to enter it again, making it
> impossible for the post-commit script to work.
[snip]
I don't even think your hook script needs to access the repository in
a way that requires a password. You should be able to bypass that.
For example, you could write your post-commit hook like this:
#!/bin/sh
REPOS="$1"
REV="$2"
SVNADMIN=/usr/bin/svnadmin
MKTEMP=/usr/bin/mktemp
CAT=/bin/cat
RM=/bin/rm
FILE=`$MKTEMP -t svnhook`
$CAT > $FILE << SVNHOOK_EOF
my
new
log
message
SVNHOOK_EOF
$SVNADMIN setlog --bypass-hooks \
$REPOS -r $REV $FILE
$RM -f $FILE
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 13 21:20:52 2007