修复SVN校验和 [英] Repair SVN Checksum

问题描述

我在 Flex Builder 3 中使用 subclipse，最近在尝试提交时收到此错误:

I'm using subclipse in Flex Builder 3, and recently received this error when trying to commit:

svn:'/Users/redacted/Documents/Flex Builder 3/path/to/my/file.mxml' 的校验和不匹配；预期:'f8cb275de72776657406154dd3c10348'，实际:'null'

我通过以下方式解决了这个问题:

I worked around it by:

1. 提交所有其他更改的文件，省略麻烦的文件.
2. 将故障文件的内容复制到 TextMate 窗口
3. 在 FlexBuilder/Eclipse 中删除我的项目
4. 从 SVN 中检查我的项目
5. 从 TextMate 窗口复制故障文件的文本
6. 提交更改.

它奏效了，但我不禁想到还有更好的方法.究竟是什么导致了 svn:checksum 错误，最好的解决方法是什么.

It worked, but I can't help but think there's a better way. What's actaully happening to cause the svn:checksum error, and what's the best fix.

也许更重要——这是更大问题的征兆吗?

Maybe more important -- is this a symptom of a greater problem?

推荐答案

.svn 目录中的文件，用于跟踪您已检出的内容、时间、修订版以及从何处以某种方式损坏，为此特定文件.

The file in the .svn directory that keeps track of what you have checked out, when, what revision, and from where, has gotten corrupted somehow, for that particular file.

这并不比普通的奇怪文件问题更危险或更严重，并且可能是由于各种问题，例如颠覆程序在更改过程中死亡、电源中断等.

This is no more dangerous or critical than the normal odd file problem, and can be because of various problems, like a subversion program dying mid-change, power-disruption, etc.

除非它发生得更多，否则我不会从中受益.

Unless it happens more I wouldn't make much out of it.

它可以通过做你所做的事情来修复，复制你的工作文件，签出一个新的副本，然后重新添加修改过的文件.

It can be fixed by doing what you did, make a copy of your work-files, check out a fresh copy, and add the modified files back in.

请注意，如果您有一个繁忙的项目，通常必须合并更改，这可能会导致问题.

Note that this might cause problems if you have a busy project where you would normally have to merge in changes.

例如，您和一位同事都检查了一个新副本，然后开始处理同一个文件.在某些时候，您的同事会检查他的修改.当您尝试这样做时，您会遇到校验和问题.如果您现在制作更改文件的副本，重新签出，那么 Subversion 将无法跟踪您的更改应如何合并回.

For instance, you and a collegue both check out a fresh copy, and start working on the same file. At some point, your collegue checks in his modifications. When you attempt to do the same, you get the checksum problem you have. If you now make copies of your changed files, do a fresh checkout, then subversion will lose track of how your changes should be merged back in.

如果在这种情况下您没有遇到问题，那么当您准备签入您的修改时，您需要先更新您的工作副本，并可能处理与您的文件的冲突.

If you didn't get the problem in this case, when you got around to checkin in your modifications, you would need to update your working copy first, and possibly handle a conflict with your file.

但是，如果您重新结帐并完成同事的更改，现在看起来您删除了他的更改并替换为您自己的更改.没有冲突，也没有来自 Subversion 的迹象表明出现了问题.

However, if you do a fresh checkout, complete with your collegues changes, it now looks like you removed his changes and substituted with your own. No conflicts, and no indications from subversion that something is amiss.

这篇关于修复SVN校验和的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！