Nathaniel,

Thanks for the reply.  I have now been able to delete the lock and
resume the synsync. So it looks like it was exactly as you said.

On Mar 16, 4:16 am, Nathaniel Manista <[email protected]> wrote:
> On Thu, Mar 15, 2012 at 6:51 PM, Janet Heffernan <[email protected]>wrote:
>
>
>
>
>
>
>
>
>
> > I am trying to use svnsync to transfer content from an existing repo
> > to a Google Code repo.  The Google Code project name is texmex.
>
> > At revision 144 of the svnsync the process failed with this output:
>
> > Copied properties for revision 143.
> > Transmitting file data .
> > Committed revision 144.
> > Copied properties for revision 144.
> > svnsync: E160000: Commit failed unexpectedly --- please try again
> > later (1)
>
> > Next I tried to continue by calling svnsync again:
>
> > C:\Users\jan\Desktop>svnsync sync --username [email protected]
> >https://texmex.googlecode.com/svn/
> > svnsync: warning: W200007: Target server does not support atomic
> > revision property edits; consider upgrading it to 1.7 or using an
> > external locking pr
> > ogram
> > Failed to get lock on destination repos, currently held by 'KRONG:
> > 4d933812-0e40-ae4f-b601-2ad896ca5edc'
> > Failed to get lock on destination repos, currently held by 'KRONG:
> > 4d933812-0e40-ae4f-b601-2ad896ca5edc'
> > Failed to get lock on destination repos, currently held by 'KRONG:
> > 4d933812-0e40-ae4f-b601-2ad896ca5edc'
> > Failed to get lock on destination repos, currently held by 'KRONG:
> > 4d933812-0e40-ae4f-b601-2ad896ca5edc'
> > Failed to get lock on destination repos, currently held by 'KRONG:
> > 4d933812-0e40-ae4f-b601-2ad896ca5edc'
> > Failed to get lock on destination repos, currently held by 'KRONG:
> > 4d933812-0e40-ae4f-b601-2ad896ca5edc'
> > Failed to get lock on destination repos, currently held by 'KRONG:
> > 4d933812-0e40-ae4f-b601-2ad896ca5edc'
> > Failed to get lock on destination repos, currently held by 'KRONG:
> > 4d933812-0e40-ae4f-b601-2ad896ca5edc'
> > Failed to get lock on destination repos, currently held by 'KRONG:
> > 4d933812-0e40-ae4f-b601-2ad896ca5edc'
> > Failed to get lock on destination repos, currently held by 'KRONG:
> > 4d933812-0e40-ae4f-b601-2ad896ca5edc'
> > svnsync: E000022: Couldn't get lock on destination repos after 10
> > attempts
>
> > My computer is called KRONG so this kind of makes sense.
>
> > A quick websearch suggests that I simply need to delete the revision
> > property named svn:sync-lock on revision 0 of the repository.  I do
> > this:
>
> > C:\Users\jan\Desktop>svn propdel svn:sync-lock --revprop -r 0
> >https://texmex.googlecode.com/svn/
> > property 'svn:sync-lock' deleted from repository revision 0
>
> > But the attempt to restart svnsync fails exactly as above.  When I
> > look at the revision properties for revision 0 of the repo,  svn:sync-
> > lock is still present.  I try to delete it with the Tortoise repo-
> > browser.  Again, it appears to be deleted successfully, but if I re-
> > open the revision properties dialog, the prop is still there.
>
> > Next I try to reset the repo and start again but that fails with error
> > 500.
>
> > 500. That’s an error.
>
> > The server encountered an error and could not complete your request.
>
> > If the problem persists, please report your problem and mention this
> > error message and the query that caused it. That’s all we know.
>
> > At this point I am all out of ideas.  Can anyone suggest a
> > resolution.  I would be happy to have the repo reset by admins so that
> > I can try svnsync again.
>
> > On the client side I am using TortoiseSVN 1.7.2.  My svn command line
> > tools are the ones bundled with Tortoise.  I'm on Win7 x64.
>
> We suffered a service interruption of several hours and have only just in
> the last hour recovered.
> Does this problem persist?
> -Nathaniel

-- 
You received this message because you are subscribed to the Google Groups 
"Project Hosting on 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.

Reply via email to