Les Mikesell <lesmikes...@gmail.com> writes: > Perhaps it is obvious and known to you. I think the number of error > reports on the list indicates that the scenarios that cause errors are > not generally well understood.
The error in this case: line 1935: assertion failed (svn_checksum_match(entry_md5_checksum, found_md5_checksum)) indicates that the working copy is corrupt. This is not a problem that can be solved by running cleanup. It's possible that it could be solved in other ways (by running "svn up -r0" on the affected files perhaps, or "rm -rf on a subdir) but it's still risky to upgrade a corrupt working copy as we don't know what other corruption is present. It's possible that the corruption has lain dormant in the 1.6 working copy for some time, the corrupt checksum will only be reconised when an update or commit attempts to explicitly modify the file with a problem. Other 1.6 operations won't examine the corrupt checksum. However the 1.7 upgrade has to recalculate checksums for all the files so it falls over on such cases. One of the things we would like to do is verify that this really is corruption but that is hard because the error message isn't very good (1.7.1 will do better--it will tell you which file has the problem) and our users don't always have the tools to do it. We need sombody capable of debugging the assertion to identify the file, and then checking the stored checksum against the actual checksum. Alternatively somebody who can validate all the the checksums in the working copy to see if any are wrong. Or somebody who is prepared to send their working copy to me so that I can do it. -- Philip
