• git svn rebase出现了checksum mismatch的错误


    http://stackoverflow.com/questions/3156744/git-svn-rebase-checksum-mismatch

    This solution was the only one that worked for me:

    See what was the revision number of the last change on the file:

    git svn log chrome/test/functional/search_engines.py

    Reset svn to be closest parent before that revision:

    git svn reset -r62248 -p

    Do a git svn fetch!

    Dance at your success.

    When I update suuuuuper old Chromium repositories, I occasionally get that stupid Checksum mismatch from svn. It happens often enough that it's a thing, but uncommonly enough that I forget how to fix it each time. So, FOR PROSPERITY:

    Checksum mismatch: trunk/src/chrome/test/functional/search_engines.py 5d1082dfc3e6363ece792d7cd49fde0a7ce9c6df
    expected: e88e3ea6349cb44955d58e6a3964824f
    got: af58cced63097504e4bfb6574c252f4a

    Then proooobably what happens was search_engines.py downloaded wonky or something such that the hash no longer came to be the correct thing. So solution:

    See what was the revision number of the last change on the file:
    git svn log chrome/test/functional/search_engines.py

    Reset svn to be closest parent before that revision:
    git svn reset -r62248 -p

    Do a git svn fetch!

    Dance at your success.

    总结:

    出现这个情况,原因是,在同步svn服务器代码的时候出错了,仔细查看结果,发现同步到的对应文件的最后一次提交,更新失败了。

    但是,那一次提交仍然被记录下来。

    $ git svn rebase
    Checksum mismatch: ZITaker/UI/TableForm.cs
    expected: 1d341c96dacd486b6f071461b791f209
        got: 605022e72af5d950f6cd32ad5fd157aa

    找到TableForm.cs文件的最后一次日志的svn版本号,目前找到是1701

    使用git svn reset -r1701 -p

  • 相关阅读:
    最小生成树+BFS J
    Noip 2016
    舒适的路线 (code[vs] 1001)
    拦截导弹 (加了神奇的位运算)
    逃出克隆岛 (codevs 2059)
    回家(洛谷 P1592)
    热浪
    城堡
    笔记 (一道正解思路巧妙的题)
    脱水缩合
  • 原文地址:https://www.cnblogs.com/chucklu/p/4922366.html
Copyright © 2020-2023  润新知