It looks like svnsync committed up through r35, but somehow it didn't track this in its 'svn:sync-last-merged-revision' property, which is still lagging at 30. Just modify that property on revision 0 to be 35:
$ svn proplist -v --revprop -r0 https://powermock.googlecode.com/svn $ svn propset --revprop -r0 svn:sync-last-merged-revision 35 https://powermock.googlecode.com/svn Then you should be able to keep syncing. On Wed, Sep 3, 2008 at 6:07 AM, Jan Kronquist <[EMAIL PROTECTED]> wrote: > > Hi > > I am trying to migrate a project from sourceforge to google code and > have a problem with svncync: > > svnsync sync https://powermock.googlecode.com/svn/ > svnsync: Revision being currently copied (35), last merged revision > (30), and destination HEAD (35) are inconsistent; have you committed > to the destination without using svnsync? > > I havenät commited anything that I know of... Now I can't continue the > sync! > > During the sync there was a couple of network problems like: > > Copied properties for revision 28. > svnsync: MERGE request failed on '/svn' > svnsync: MERGE of '/svn': 502 Bad Gateway (https:// > powermock.googlecode.com) > > I tried to create a sync to local repository and that worked fine. > > Do I need to reset the google code svn and start again? Or what should > I do? > > /Jan > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en -~----------~----~----~----~------~----~------~--~---
