svnadmin加载错误

发布于 2024-08-03 20:56:03 字数 214 浏览 13 评论 0原文

我在尝试恢复从另一台机器获取的 svn 存储库时遇到错误。错误是

svnadmin:转储流包含格式错误的标头(没有“:”)

转储是在 Subversion 1.5 服务器上创建的,我正在加载到新的 Subversion 1.6 服务器。我能够将其他几个存储库成功加载到新服务器。新服务器是 VisualSVN Server。

I am getting an error when trying to restore a svn repository taken from another machine. The error is

svnadmin: Dump stream contains a malformed header (with no ':') at

The dump was created on a subversion 1.5 server and I am loading to a new subversion 1.6 server. I was able to load several other repositories successfully to the new server. The new server is VisualSVN Server.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(5

夜还是长夜 2024-08-10 20:56:03

首先尝试清理您的转储

grep --binary-files=text -v '^* Dumped revision' ./repository.dump > ./repository.clear-dump

,然后尝试加载新的干净转储

svnadmin load /new/path/to/your/repository < ./repository.clear-dump

Try to cleanup your dump first

grep --binary-files=text -v '^* Dumped revision' ./repository.dump > ./repository.clear-dump

then try to load the new clean dump

svnadmin load /new/path/to/your/repository < ./repository.clear-dump
我的痛♀有谁懂 2024-08-10 20:56:03

据我所知(我看不到转储..),这是通过将 stdout 和 stderr 通过管道传输到转储文件中来发生的。

因此,您应该再次转储并仅将 stdout 放入转储文件中。

您在转储存储库时看到输出了吗(“*转储修订版 10”、“*转储修订版 11”等)?

as far as I know (I cannot see the dump..), this happens by piping the stdout and stderr into the dumpfile.

So you should dump again and only take stdout into your dump file.

Did you see the output while dumping the repository("*Dumped revision 10", "*Dumped Revision 11" ..etc)?

甜味超标? 2024-08-10 20:56:03

我也有同样的问题。

我想导入在 Linux Box 上创建的转储文件。该文件已被“tar”和 gzip 压缩。

我的文件是“tar.gz”,

我使用 Winzip 对其进行解压缩,但无法使用 cygwin 上传它。

然后我使用 cygwin 命令 tar -xvzf 解压缩它,然后我能够将它加载到我的新存储库中。

I had the same problem.

I wanted to import a dump file created on a Linux Box. The file has been "tar" and gzipped.

My file was a "tar.gz"

I used Winzip to uncompressed it and I couldn't upload it using cygwin.

Then I used cygwin command tar -xvzf to unzip it and I was able to load it into my new repository.

吹泡泡o 2024-08-10 20:56:03

我想补充一下。我和 Luc M 遇到了同样的问题。我的 svnadmin load REPO_PATH < file.svn 命令不起作用,错误很神秘,我无法解决。因此,我尝试在我拥有的 tar 文件上再次使用 Cygwin 安装中的 tar.exe,然后它就工作了。我还有一个已压缩的 tar 文件,但我使用 WinZip 来提取 TAR,我认为这已损坏了它。

I wanted to add. I had the same problem as Luc M. My svnadmin load REPO_PATH < file.svn command just would not work, the error was cryptic, I could not work it out. So I tried using tar.exe from my Cygwin install again on the tar file that I had and presto it worked. I also had a tar file that had been zipped, but I used WinZip to extract the TAR and I think that corrupted it.

猥琐帝 2024-08-10 20:56:03

我最近也收到了同样的消息,最后,碰巧我通过 FTP 传输了 SVN 转储,而没有明确要求二进制传输,因此转储已以 ASCII 格式传输。由于 FTP 服务器是 Windows 计算机,因此转储已因 Windows 行尾而损坏。因此,我的建议如下:检查你的线路末端。希望这至少有一点帮助。

I've had the same message recently, and in the end, it happened that I had transferred SVN dumps by FTP without explicitly asking for binary transfers, so the dumps had been transferred in ASCII format. Since the FTP server was a Windows machine, the dumps had been corrupted with Windows line ends. Therefore, my recommendation is the following: check your line ends. Hope this helps at least a little.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文