God, bedtime for me. Sorry the patch includes a conflicting diff that
can be ignored (keep the sage-2.7 version) for revision:
http://www.ms.uky.edu/~jack/sage/hg/sage-permgps-bugfix/rev/b37a82329af1
(add dollars to documentation).
The diffs:
http://www.ms.uky.edu/~jack/sage/hg/sage-permgps-bugf
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
h
> Aha! I am new at python and misunderstood how hg was working. All the
> file "hg" does is import stuff from python, so it doesn't matter which
> copy of hg I use, it matters which copy of python. The debian
> supplied hg is broken, but the sage-2.6 version of hg works fine.
>
> Sorry for miside
Aha! I am new at python and misunderstood how hg was working. All the
file "hg" does is import stuff from python, so it doesn't matter which
copy of hg I use, it matters which copy of python. The debian
supplied hg is broken, but the sage-2.6 version of hg works fine.
Sorry for misidentifying th
On 7/21/07, Jack Schmidt <[EMAIL PROTECTED]> wrote:
> This appears to be an amd64 related bug.
>
> The 64bit version:
>
> $ wget -q http://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
> $ ta
This appears to be an amd64 related bug.
The 64bit version:
$ wget -q http://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
That is very strange. My md5sum is the same.
$ md5sum spkg/standard/sage-2.7.spkg
07de6836d75b3fab84555d130f7d5f38 spkg/standard/sage-2.7.spkg
$
The error occurs with debian's hg, sage-2.7's hg, and even sage 2.6's
hg:
$ ~/sage/sage-2.6/local/bin/hg up
abort: 00changelog.i: no node
ec597fe01f
On 7/21/07, Jack Schmidt <[EMAIL PROTECTED]> wrote:
>
> The corruption only shows up on a few critical hg commands. Here is a
> log, with ~/sage/sage-2.7/ a fresh install from sage-2.7.tar
>
> $ cd ~/sage/sage-2.7/devel/
> $ tar -xf ../spkg/standard/sage-2.7.spkg
> $ cd sage-2.7
> $ hg verify
> c
The corruption only shows up on a few critical hg commands. Here is a
log, with ~/sage/sage-2.7/ a fresh install from sage-2.7.tar
$ cd ~/sage/sage-2.7/devel/
$ tar -xf ../spkg/standard/sage-2.7.spkg
$ cd sage-2.7
$ hg verify
checking changesets
checking manifests
crosschecking files in changese
On 7/20/07, Jack Schmidt <[EMAIL PROTECTED]> wrote:
>
> The mercurial repository contained in this tar file is corrupted
> making it impossible (for me at least) to resubmit my patches.
Could you please elaborate on why you think the hg repository
in sage-2.7.spkg is corrupted?I'd really like
10 matches
Mail list logo
