Yup, that works perfectly. Sorry, I thought I had already checked this since I ran ~/sage/sage-2.6/local/bin/hg, but that just runs the debian supplied copy of mercurial anyways.
Using the sage -hg version from the 64bit linux binary install, everything worked fine. The permutation patches at http://www.ms.uky.edu/~jack/sage/hg/sage-permgps-bugfix still apply cleanly, and still fix the problem. They also mess with "bundle" in an irrelevant way (correct a URL); feel free to ignore that mistaken commit. I'm letting sage build from source overnight, but I don't expect any more (non-fortran) issues. On Jul 21, 11:54 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > On 7/21/07, Jack Schmidt <[EMAIL PROTECTED]> wrote:> This appears to be an > amd64 related bug. > > > The 64bit version: > > > $ wget -qhttp://www.sagemath.org/dist/src/sage-2.7.tar > > $ md5sum sage-2.7.tar > > 31209ee51f2aace7e9df1a33e46fa89d sage-2.7.tar > > $ tar -xf sage-2.7.tar > > $ cd sage-2.7 > > $ tar -xf spkg/standard/sage-2.7.spkg > > $ md5sum spkg/standard/sage-2.7.spkg > > 07de6836d75b3fab84555d130f7d5f38 spkg/standard/sage-2.7.spkg > > $ cd sage-2.7 > > $ hg verify > > ^^^^^^^^^^^^^^ > > What happens if you instead try the hg that is included > in SAGE? E.g., do > > sage -hg verify > > I don't know what system-wide hg you're using above. > I.e., maybe it's your hg that is "corrupted" rather > than the SAGE hg repository? Also, perhaps relevant, > is that SAGE uses hg 0.9.4: > > was$ sage -hg version > Mercurial Distributed SCM (version 0.9.4) > > > > > checking changesets > > checking manifests > > crosschecking files in changesets and manifests > > checking files > > 0 files, 0 changesets, 0 total revisions > > $ hg up > > abort: 00changelog.i: no node > > ec597fe01fda8eeb062b808e989c2f5c1ed29698! > > $ > > > On the 32bit ubuntu machine: > > > $ wget -qhttp://www.sagemath.org/dist/src/sage-2.7.tar > > $ md5sum sage-2.7.tar > > 31209ee51f2aace7e9df1a33e46fa89d sage-2.7.tar > > $ tar -xf sage-2.7.tar > > $ cd sage-2.7 > > $ md5sum spkg/standard/sage-2.7.spkg > > 07de6836d75b3fab84555d130f7d5f38 spkg/standard/sage-2.7.spkg > > $ tar -xf spkg/standard/sage-2.7.spkg > > $ cd sage-2.7 > > $ hg verify > > checking changesets > > checking manifests > > crosschecking files in changesets and manifests > > checking files > > 1556 files, 5407 changesets, 15786 total revisions > > $ hg up > > 14 files updated, 0 files merged, 0 files removed, 0 files unresolved > > $ > > > Confusingly the version of hg in ~/sage/sage-2.6/local/bin/hg differs > > on the two machines, 0.9.1 versus 0.9.3. I don't know if that is > > significant. > > Probably. See above. > > William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
