Re: problem of sync a huge revision on mirror site

[svnswapnil]

Hi Murali,I am also getting the similar svnsync error but tricky one.svnsync:
E22: Revision being currently copied (32529), last merged revision
(32527), and destination HEAD (32527) are inconsistent; have you committed
to the destination without using svnsync?Please note I have two slave
repositories, one is getting synced appropriated, but the remote slave
always run into problem and reports sync failure many times.Then I manually
try to execute the sync command by executing svn pdel --revprop -r 0
--username svnsync --password svnsyncpassword svn:sync-lock TARGETRepoURLBut
above error is not getting resolved. Any solution for this problem, I also
wanted to understand if it is possible to change the revision getting
synced, & how? Thanks in Advance! Any help will be
appreciated.Regards,Swapnil



--
View this message in context: 
http://subversion.1072662.n5.nabble.com/problem-of-sync-a-huge-revision-on-mirror-site-tp133094p188224.html
Sent from the Subversion Users mailing list archive at Nabble.com.

Re: commit failed due to "backwards-sliding source views" - what do I do?

[svnswapnil]

Do we have any solution on this problem, I am also facing this issue
intermittently "svn diff has backwards sliding source views commit error
from slave repository", Is it really associated with some antivirus, then
exactly what needs to be done to address it.

Currently only work-around which has worked for me is, relocate the working
copy to master URL and do the check-in.
SVN version Used are: 1.7.8 ( server & tortoise svn client ) 
I wan't to avoid this issue going forward, any steps to solve this problem
would be great help, thanks!

Regs,
Swapnil



--
View this message in context: 
http://subversion.1072662.n5.nabble.com/commit-failed-due-to-backwards-sliding-source-views-what-do-I-do-tp104150p190425.html
Sent from the Subversion Users mailing list archive at Nabble.com.