通过 svnsync 复制 SVN 存储库时如何解决此错误? [英] how do I work around this error while copying SVN repository by svnsync?

查看:22
本文介绍了通过 svnsync 复制 SVN 存储库时如何解决此错误?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在使用 svnsync 复制存储库,并且每次都在同一修订版上收到此错误.

I am copying a repository by using svnsync and am receiving this error on the same revision every time.

传输文件数据...svnsync:'https://svn1.avlux.net/的报告xxxxxx.net':无法读取响应正文:安全连接被截断 https://svn1.avlux.net)

Transmitting file data ...svnsync: REPORT of 'https://svn1.avlux.net/xxxxxx.net': Could not read response body: Secure connection truncated https://svn1.avlux.net)

这是一个很大的修订版,我没有对服务器的管理员访问权限.有没有办法解决这个问题,即使它涉及手动检出和复制修订版?

It is a large revision and I don't have admin access to the server. Is there a way around this, even if it involves checking out and copying the revision manually?

推荐答案

你是想复制一次 repo 还是想设置一个持续的镜像方案?

Are you just trying to copy the repo once or are you trying to setup an ongoing mirroring scheme?

如果是前者,您可以让同步一直进行,直到它失败,然后在它失败的修订版和之前的修订版之间做一个差异,然后将其输出到文件中.因此,如果失败的 rev 是 135,它将是这样的:

If it's the former you could let sync go until it fails, then do a diff between the revision it failed on and the previous revision and output that to a file. So if the rev that failed was 135 it would be something like this:

svn diff -r134:135 http://your/repo/url > patch.diff

然后您可以将此补丁文件应用到新存储库的工作副本.

Then you can apply this patch file to a working copy of the new repo.

patch -p0 -i patch.diff

然后将更改提交到该工作副本并再次启动 svnsync.

Then just commit the changes to that working copy and kick off svnsync again.

这很骇人听闻,但它可能会奏效.

This is pretty hackish, but it might work.

注意:我没有测试任何命令,可能存在一些语法错误,但一般方法理论上应该可行.

NOTE: I didn't test any of the commands, there might be some syntax errors, but the general approach should work in theory.

这篇关于通过 svnsync 复制 SVN 存储库时如何解决此错误?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆