You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by David Aldrich <Da...@EU.NEC.COM> on 2011/04/04 10:53:07 UTC

"Cannot copy revprops for a revision that has not been synchronized yet."

Hi

We maintain a mirrored offsite svn repository for backup purposes.  The svnsync process is run every 15 mins by a cron job.

We have recently installed a post-revprop-change hook to allow users to change a revision's log message.  The hook copies the rev prop change to the mirror:

svnsync copy-revprops

However, this gives a problem when the revision property change is made before the cron job has copied the revision to the mirror. In that case, the hook fails with the error:

"Cannot copy revprops for a revision that has not been synchronized yet."

I guess this is an issue that others have faced. Please can someone suggest a solution?

Best regards

David

RE: "Cannot copy revprops for a revision that has not been synchronized yet."

Posted by David Aldrich <Da...@EU.NEC.COM>.
> Just ignore that particular error?  When the cron eventually runs, it will see
> the new log message.

Of course, thanks.

David

Re: "Cannot copy revprops for a revision that has not been synchronized yet."

Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Just ignore that particular error?  When the cron eventually runs, it
will see the new log message.

David Aldrich wrote on Mon, Apr 04, 2011 at 09:53:07 +0100:
> Hi
> 
> We maintain a mirrored offsite svn repository for backup purposes.  The svnsync process is run every 15 mins by a cron job.
> 
> We have recently installed a post-revprop-change hook to allow users to change a revision's log message.  The hook copies the rev prop change to the mirror:
> 
> svnsync copy-revprops
> 
> However, this gives a problem when the revision property change is made before the cron job has copied the revision to the mirror. In that case, the hook fails with the error:
> 
> "Cannot copy revprops for a revision that has not been synchronized yet."
> 
> I guess this is an issue that others have faced. Please can someone suggest a solution?
> 
> Best regards
> 
> David