Hi, I am having difficulty synchronizing a repository from SourceForge with a mirror repository at Google Code. The problem seems to be with the short duration of the SourceForge connection timeout. Because of a large replacement operation at r2025 of the source repository, the connection to SourceForge always times out before the "svnsync synchronize" operation has gathered the revision data for transmission to the mirror repository, even after many tries.
Is there a workaround or a solution to the short SourceForge connection timeout? I thought that using svnadmin dump/load for only the large revision, r2025, may work and then resume syncing, but it seems that is not supported by Google Code. (error message and svn log for r2025 below) Thank you for your help! Sam _timeout message_ > svnsync initialize --username [email protected] https://mesa -mirror.googlecode.com/svn http://mesa.svn.sourceforge.net/svnroot/mesa Copied properties for revision 0. > svnsync synchronize https://mesa-mirror.googlecode.com/svn Committed revision 1. Copied properties for revision 1. Transmitting file data ... ... Committed revision 2024. Copied properties for revision 2024. svnsync: REPORT of 'http://mesa.svn.sourceforge.net/svnroot/mesa': Could not read response body: Connection reset by peer (http://mesa .svn.sourceforge.net) -- You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-code-hosting/-/ON6tKtlnSm8J. 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.
