[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Error encountered when trying to edit log for a revision

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Fri, 23 Oct 2009 14:45:07 +0100

2009/10/23 Silverman, Joshua H (IS) <Josh.Silverman_at_ngc.com>:
> When I tried to edit the log to alter the revision's description (no code
> update, simply the description itself), I got the following error:
>
> DAV request failed; it's possible that the repository's pre-revprop-change
> hook
> either failed or is non-existent
> At least one property change failed; repository is unchanged
> Error setting property 'log':
> Repository has not been enabled to accept revision propchanges;
> ask the administrator to create a pre-revprop-change hook
>
> What do the administrator need to do to create the pre-revprop-change hook?
> He is not a Subversion expert, so he asked me to inquire.

You need to create a hook within the hooks directory of the
repository. What that looks like will depend on your OS. If it is
Linux you can use one of the template scripts already in that
directory (just need to rename and modify as required). If you have a
Windows repo server there is a sample batch file in our docs.

http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-repository-hooks.html

What that doesn't mention, although it is kinda obvious, is that the
batch file should be called pre-revprop-change.bat

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2410644
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-10-23 15:45:11 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.