checksum mismatch
Hi There, I have a slightly annoying problem, I get this error after changing an already existing file. see below Base checksum mismatch on 'morris2.css': expected: e15c569c06e9357eca0c3a619a86d883 actual: ab16f2c7fcc8ac34951dd2e31e176216 If a remove the latest change in this file, it works again but as soon if I would like to commit a change, I get this error. I already tried to remove the old morris.css (hence; morris2.css in thje error) but after I made the same change in this file, the error returned At first I thought, maybe something inside my file was causing the error (because is did work after removing the last change) , like an not allowed character... but every change I made is causing this error (except getting back to the 'old' situation before the error...) Anyone? -- You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com. To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/versions?hl=en.
Re: checksum mismatch
Hi Piet, First of all, welcome to the group! The problem you describe is usually the result of accidentally making changes to a copy of one of your files that's inside a ".svn" folder inside your working copy. Every working copy has these folders with metadata in them, they describe the contents of the folder they're in and every sub-folder than has its own ".svn" folder. One of the most important parts of the metadata is the original version of your files, from before you made any changes. This is the so-called BASE revision. Because these extra copies of the files exist, you're able to "Revert" without needing a connection to your repository. Along with those BASE revisions, the ".svn" folder also contains checksums of those files and the mismatch happens when you accidentally edit one of the files, therefore making its contents no longer match with the checksum. The best way to solve this is: 1. to isolate the files you have made changes to that you want to keep (as in, commit back to the repository when you have a chance). 2. to delete the folder that contains those files locally (from the Finder, not from Versions) in your working copy, making it "missing". 3. to update your working copy, thereby getting an uncorrupted version of the folder back, 4. to place your changed files back in their applicable locations and to try and commit again. Now, because every sub-folder has it's own ".svn" admin area, moving folders back and forth is not recommended and can be a bit of a recipe for headaches. You're best off trying to move individual files back in to where they should be placed. In step 2, if your files are at the top level of your working copy, this may mean checking out an entirely fresh working copy. In such a case, I'd recommend checking it out next to the corrupted one, and if you have a lot of changes, use e.g. FileMerge (Kaleidoscope doesn't have a folder comparison feature yet), to see exactly which files are different between your original one and the fresh working copy. Then, copy over those changed files (except for the ones inside ".svn" folders of course) until they match. This way, you know you won't have lost any work. The good news is that this whole situation shouldn't happen very often, the bad news is that there's really not an easy way to have Versions, or another Subversion client for that matter, just fix things up for you. Drop us a line if you need more help with this. Cheers, - Dirk Stoop the Versions team On Mar 30, 10:53 am, piet wrote: > Hi There, > > I have a slightly annoying problem, I get this error after changing an > already existing file. see below > > Base checksum mismatch on 'morris2.css': > expected: e15c569c06e9357eca0c3a619a86d883 > actual: ab16f2c7fcc8ac34951dd2e31e176216 > > If a remove the latest change in this file, it works again but as soon > if I would like to commit a change, I get this error. I already tried > to remove the old morris.css (hence; morris2.css in thje error) but > after I made the same change in this file, the error returned > > At first I thought, maybe something inside my file was causing the > error (because is did work after removing the last change) , like an > not allowed character... but every change I made is causing this error > (except getting back to the 'old' situation before the error...) > > Anyone? -- You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com. To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/versions?hl=en.
Re: checksum mismatch
Thanks Dirk, It's a lot better know (as in solved : )) Cheers, Piet On Mar 30, 3:11 pm, Dirk Stoop wrote: > Hi Piet, > > First of all, welcome to the group! > > The problem you describe is usually the result of accidentally making > changes to a copy of one of your files that's inside a ".svn" folder > inside your working copy. > > Every working copy has these folders with metadata in them, they > describe the contents of the folder they're in and every sub-folder > than has its own ".svn" folder. One of the most important parts of the > metadata is the original version of your files, from before you made > any changes. This is the so-called BASE revision. Because these extra > copies of the files exist, you're able to "Revert" without needing a > connection to your repository. > > Along with those BASE revisions, the ".svn" folder also contains > checksums of those files and the mismatch happens when you > accidentally edit one of the files, therefore making its contents no > longer match with the checksum. > > The best way to solve this is: > 1. to isolate the files you have made changes to that you want to keep > (as in, commit back to the repository when you have a chance). > 2. to delete the folder that contains those files locally (from the > Finder, not from Versions) in your working copy, making it "missing". > 3. to update your working copy, thereby getting an uncorrupted version > of the folder back, > 4. to place your changed files back in their applicable locations and > to try and commit again. > > Now, because every sub-folder has it's own ".svn" admin area, moving > folders back and forth is not recommended and can be a bit of a recipe > for headaches. You're best off trying to move individual files back in > to where they should be placed. > > In step 2, if your files are at the top level of your working copy, > this may mean checking out an entirely fresh working copy. In such a > case, I'd recommend checking it out next to the corrupted one, and if > you have a lot of changes, use e.g. FileMerge (Kaleidoscope doesn't > have a folder comparison feature yet), to see exactly which files are > different between your original one and the fresh working copy. Then, > copy over those changed files (except for the ones inside ".svn" > folders of course) until they match. This way, you know you won't have > lost any work. > > The good news is that this whole situation shouldn't happen very > often, the bad news is that there's really not an easy way to have > Versions, or another Subversion client for that matter, just fix > things up for you. > > Drop us a line if you need more help with this. > > Cheers, > - Dirk Stoop > > the Versions team > > On Mar 30, 10:53 am, piet wrote: > > > Hi There, > > > I have a slightly annoying problem, I get this error after changing an > > already existing file. see below > > > Base checksum mismatch on 'morris2.css': > > expected: e15c569c06e9357eca0c3a619a86d883 > > actual: ab16f2c7fcc8ac34951dd2e31e176216 > > > If a remove the latest change in this file, it works again but as soon > > if I would like to commit a change, I get this error. I already tried > > to remove the old morris.css (hence; morris2.css in thje error) but > > after I made the same change in this file, the error returned > > > At first I thought, maybe something inside my file was causing the > > error (because is did work after removing the last change) , like an > > not allowed character... but every change I made is causing this error > > (except getting back to the 'old' situation before the error...) > > > Anyone? -- You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com. To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/versions?hl=en.
