Svn checksum mismatch while updating expected
I've blown away my working copy of the repo and re-checked out and the problem goes away for a while and then returns. What causes this and how I can prevent it from happening in the future? Is there an easier way then blowing away my WC and re-checking out to fix it? -- Aaron Turner Twitter: @synfinatic - Pcap editing and replay tools for Unix & Windows Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety.-- Benjamin Franklin "carpe diem quam minimum credula postero" I am hoping your repository is being served via https:// protocol.Is your hard drive in good working condition (no bad sectors, not on the verge of a crash? What if you attempt from another computer on the network?Use a different physical drive in your computer for the working copy?A benefit of my way over other procedures I’ve seen described is that I didn’t have to do anything special to get back to a state where I could commit the latest changes I had made.
If that’s enough assurance for you, let’s get this road on the show.
Before committing (saving) a file, SVN compares the latest revision of the file in the repository with the corresponding, locally saved, latest revision. If the checksum for a file changes, you know it has been altered.