blocks|key|585002|text|修复它的最简单方法(如果您没有太多更改)是将您的更改复制到另一个目录，删除签出项目的目录，然后再次签出项目。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|585003|然后将您的更改复制回(不复制任何.svn文件夹)并提交，然后继续。|585004|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The easiest way to fix it (if you don't have many changes) is to copy your changes to another directory, delete the directory where your project is checked out, and checkout the project again.

Then copy your changes back in (don't copy any .svn folders) and commit, and continue.

blocks|key|585046|text|这发生在我使用Eclipse插件和同步的时候。导致问题的文件没有本地更改(事实上，自我上次更新以来也没有远程更改)。我为文件选择了"revert“，没有对文件进行其他修改，一切都恢复正常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|585047|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This happened to me using the Eclipse plug-in and synchronizing. The file causing the issue had no local changes (and in fact no remote changes since my last update). I chose "revert" for the file, with no other modifications to the files, and things returned to normal.

blocks|key|369372|text|我有一个相同的错误，但对于一个文件。在IntelliJ+IDEA中，我能够复制文件，然后进入项目并删除有问题的文件，然后成功提交。然后，我创建了一个同名的新文件，并将内容复制回其中。我猜您可能会丢失修订历史，但它确实可以工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|369373|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had a the same error but for one file. In IntelliJ IDEA I was able to make a copy of the file, then go into the project and delete the file in question, then commit successfully. Then, I made a new file with the same name and copy the contents back into it. I guess you would lose the revision history but it does work.

blocks|key|585113|text|在服务器上有类似的问题，但SVN目录非常大，不想删除和重新同步，所以我只是在本地复制了文件，然后删除了它们。更新成功并将文件添加回。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|585114|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

had a similiar issue on a server but the SVN directory was very large , didn't want to delete and resync so I just made a copy of the files locally and then deleted them. When update succeeded and added files back in.

blocks|key|585161|text|尝试删除该文件，并从.svn目录下的文件条目中移除该文件引用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|585162|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

try to delete the file and remove the file reference from file entries under the .svn directory

blocks|key|585189|text|我有一个类似的问题。主要供应商是杀毒软件"FortiClient“(杀毒软件%2B虚拟专用网络CLient)。当我禁用它时-所有的更新/签出都是正确的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|585190|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had a simllar problem. Main provider was antivirus "FortiClient" (antivirus + VPN CLient). When I disabled it - all update/checkout was made correctly

blocks|key|369523|text|我遇到了类似的错误，修复方法如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|369524|(我的“修复”是基于一个假设，这个假设可能是正确的，也可能不是，因为我不太了解subversion内部是如何工作的，但它肯定对我有效)|369525|我假设.svn\text-base\import.php.svn-base应该与最新的提交匹配。|369526|当我检查我有错误的文件时，基本文件与存储库中的最新提交不匹配。|369527|我复制了最近一次提交的文本，并将其保存在.svn文件夹中，替换了错误的文件(制作了备份副本，以防我的假设出错)。(文件被标记为只读，我清除了该标记，覆盖并将其重新设置为只读)|369528|然后我就可以成功地提交了。|369529|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

I had a similar error and fixed as follows:

(My 'fix' is based on an assumption which may or may not be correct as I don't know that much about how subversion works internally, but it definitely worked for me)

I am assuming that .svn\text-base\import.php.svn-base is expected to match the latest commit.

When I checked the file I was having the error on , the base file did NOT match the latest commit in the repository.

I copied the text from the latest commit and saved that in the .svn folder, replacing the incorrect file (made a backup copy in case my assumptions were wrong). (file was marked read only, I cleared that flag, overwrote and set it back to read only)

I was then able to commit successfully.

blocks|key|585274|text|如果你有一位同事和你一起工作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|585275|1)要求他重命名导致问题和commit的文件|offset|length|style|CODE|585276|2)你update+(现在你看到的文件与无效的校验和不同的名称)|585277|3)将其重命名为原始名称|585278|4)+commit+(并请您的同事到update找回初始状态的文件名)|585279|这为我解决了这个问题。|585280|entityMap^0|0|D|6|0|3|6|0|0|3|6|I|6|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|Z|8|@$D|10|E|11|F|G]|$D|12|E|13|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|14|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|Q|$]]

If you have a colleague working with you:

1) ask him to rename the file causing problems and <code>commit</code>

2) you <code>update</code> (now you see the file with invalid checksum with different name)

3) rename it back to its original name

4) <code>commit</code> (and ask you colleague to <code>update</code> to get back the file name in its initial state)

This solved the problem for me.

blocks|key|369602|text|1.'update+to+reversion‘检查目录下的'only+this+item’2.更新再次检查‘完全递归’|type|unstyled|depth|inlineStyleRanges|entityRanges|data|369603|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

1.'update to reversion' check 'only this item' under the directory
2.update again check 'Fully recursive'

blocks|key|369644|text|我正在使用乌龟SVN，在尝试了这个页面中的所有解决方案但没有工作后，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|369645|我终于备份了问题文件。并使用Repo+Browser删除其中的问题文件，然后更新本地文件夹，以便删除本地文件夹中的文件。然后复制备份文件和Add+>+Commit，这样我就可以成功更新了。|offset|length|style|CODE|369646|此方法的唯一缺点是此文件的历史记录将被删除。|369647|entityMap^0|0|E|C|1X|C|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]|$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

I'm using Tortoise SVN, after tring all solution in this page and not working, 

I finally back up the problem file. and use <code>Repo Browser</code> delete the problem file in it, then update local folder so the file in local folder is deleted. Then copy back the backup file and <code>Add &gt; Commit</code>, then I can update successfully.

The only disadvantage of this method is the history of this file will be removed.

When I try to update some files from Subversion, I get the error:

<pre><code>org.tigris.subversion.javahl.ClientException: 
Checksum mismatch while updating 'D:\WWW\Project\\.svn\text-base\import.php.svn-base'; expected: '3f9fd4dd7d1a0304d8020f73300a3e07', actual: 'cd669dce5300d7035eccb543461a961e'
</code></pre>

Why do I get this? How can I fix it?

SVN - Checksum mismatch while updating

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

当我试图从Subversion更新一些文件时，我得到了错误：org.tigris.subversion.javahl.ClientException: Checksum mismatch while updating 'D:\WWW\Project\\.svn\text-base\import.php.svn-base...

问SVN -更新时校验和不匹配
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问SVN -更新时校验和不匹配EN