On Jun 14, 2007, at 03:32, Giulio Troccoli wrote:
>> 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:
>
> [snip]
>
> Thanks. I didn't know that you could use svnadmin to change the log.
> This does not require a commit, does it?
Correct. The log message is a property of a revision, so it just
changes the property of that revision, without creating a new revision.
> However, this is more a workaround that a solution. I still don't
> understand why one user has stored the password and another hasn't
> (the
> config files in the .subversion diretory are the same). I would very
> much like to understand the problem and fix it rather than put a
> workaround in place. Especially because the exact same procedure (to
> change the log message) works perfectly fine in the production
> repository.
Oh I thought the task was to modify the log message in a hook script,
and I showed how to do that.
I don't know why you're having the other problem.
>> $SVNADMIN setlog --bypass-hooks \
>> $REPOS -r $REV $FILE
>
> The problem is not that the normal hooks are called. So bypassing them
> wouldn't make any difference. However, as I said, I didn't know you
> could use svnadmin and that this does not require a commit.
I just included --bypass-hooks for completeness. If you did not
specify that, you would also need to install a pre-revprop-change
hook to allow changing revision properties. Perhaps you have already
done this, in which case --bypass-hooks is not necessary for you. But
maybe someone reading these messages in the archive won't have
already set up that hook.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 15 08:01:58 2007