Hi Mitesh, On Sun, Nov 7, 2010 at 8:17 AM, Mitesh Patel <qed...@gmail.com> wrote: > How serious are these errors?
To me, the errors reported by "hg verify" is not serious. That's because it's trivial to recover from the error at the cost of possibly generating new hashes. Here's how to recover the whole Sage 4.6.1.alpha0 repository from errors: [mv...@sage standard]$ pwd /home/mvngu/sage-src/sage-4.6.1.alpha0-verified/spkg/standard [mv...@sage standard]$ tar -jxf sage-4.6.1.alpha0.spkg [mv...@sage standard]$ cd sage-4.6.1.alpha0 [mv...@sage sage-4.6.1.alpha0]$ hg verify <lots of errors about repository corruption> [mv...@sage sage-4.6.1.alpha0]$ cd .. [mv...@sage standard]$ mkdir sage-4.6.1.alpha0-verified [mv...@sage standard]$ hg convert --config convert.hg.ignoreerrors=True sage-4.6.1.alpha0 sage-4.6.1.alpha0-verified <lots of commit messages> [mv...@sage standard]$ rm -rf sage-4.6.1.alpha0 [mv...@sage standard]$ hg clone sage-4.6.1.alpha0-verified sage-4.6.1.alpha0 [mv...@sage standard]$ cd sage-4.6.1.alpha0 [mv...@sage sage-4.6.1.alpha0]$ hg verify checking changesets checking manifests crosschecking files in changesets and manifests checking files 3342 files, 15099 changesets, 39386 total revisions [mv...@sage sage-4.6.1.alpha0]$ hg tip changeset: 15098:e832154f36dc tag: tip user: convert-repo date: Sun Nov 07 08:19:03 2010 +0000 summary: update tags The above assumes you have the following in your ~/.hgrc: [extensions] hgext.convert = I have not tested the above recovered repository yet. -- Regards Minh Van Nguyen -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
