SVN revprop failure

[Antranig Basman]

Thanks Jamon,
Yes, I think that would be useful functionality. I think we have been 
assuming for a while that we could indeed issue revprop, since I 
remember a conversation with Colin in which he was explaining to the 
team that it was a better solution than recomitting or deleting things. 
In this case I missed a relevant JIRA number off a commit message which 
I think is a common kind of problem.
Does the hook need to do anything special? I assume it just needs to 
make the same kinds of checks that the commit hook already does, i.e. 
that the revised message still begins with a JIRA number or NOJIRA. Let 
me know if I can be any help. I look forward to the big migration of 
infrastructure :)
Cheers,
Antranig.

On 06/12/2010 15:43, Jamon Camisso wrote:
> On 12/6/2010 5:29 PM, Antranig Basman wrote:
>> A failure which might be an area related to the one I just posted about
>> is this failure I just got when trying to revise some revision
>> properties in the repository -
>>
>> " svn: DAV request failed; it's possible that the repository's
>> pre-revprop-change hook either failed or is non-existent
>> svn: Error setting property log:
>> Repository has not been enabled to accept revision propchanges;
>> ask the administrator to create a pre-revprop-change hook
>> svn: DAV request failed; it's possible that the repository's
>> pre-revprop-change hook either failed or is non-existent
>> svn: Error setting property log:
>> Repository has not been enabled to accept revision propchanges;
>> ask the administrator to create a pre-revprop-change hook"
>>
>> The command I issued was
>>
>> propset --revprop -r 10335--force "svn:log" "message"
>
> Hi Antranig,
>
> That error is by design. SVN requires that a pre-revprop-change hook
> exist in order to allow changes to past revisions, since those
> properties of a commit are not versioned within SVN.
>
> If you would like me to setup a script, I'm happy to work with you on
> one, but until such a script exists the command above will always fail.
>
> On a related note (to your previous email), I have encountered the same
> problem with long delays. Specifically, I discovered the slowdown when
> testing the post-commit script last week. I wonder if that had something
> to do with the post-commit emails not being sent as well.
>
> In any case, Colin, Jess and myself are working on getting ready to
> migrate mail and SVN onto the main virtual machine for Fluid's
> infrastructure. I am hoping that moving both mail and SVN there resolves
> the issue.
>
> Cheers, Jamon
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work