On Sun, 24 Aug 2008, William Stein wrote:
>> I am really looking for the day when I will do "apt-get install sage",
>> which is number 1 on my wish-list.
>
> That day should be very soon, I hope. (Tim Abbott -- any updates on the
> status of this?)
All the dependencies are now in Debian, but th
The Sage package is coming along. It passes the vast majority of tests,
and is usable on the command line or via the notebook. However, there are
still various issues.
The worst is the LinBox problem I described earlier involving
sage.matrix.matrix_integer_dense.Matrix_integer_dense._charpol
On Tue, 22 Jul 2008, mabshoff wrote:
>
> On Jul 21, 7:44 pm, Timothy G Abbott <[EMAIL PROTECTED]> wrote:
>> 1) Sage 3.0.4 or 3.0.5 built with polybori 0.5rc fails to find
>> m4ri_build_all_codes and m4ri_destroy_all_codes. This is discussed in
>> <http://trac.s
I figured I'd give everyone an update on how things are going with the
Sage packages. I believe (but am not certain) that all of the Sage
dependencies that I want to get into Lenny will make it, though I'm still
waiting on final review for 5 of them that had copyright problems in the
past.
O
On Mon, 21 Jul 2008, William Stein wrote:
> I do not like to call Sage a "computer algebra" system. I prefer to call
> it "mathematical software". I don't like the term "computer algebra" since
> it suggests sage is only for "computer *algebra*", whereas Sage is for
> much more than just algebra.
Below I list a large number of trivial problems in the Sage 3.0.5
distribution tarball that the Debian automatic package checking tools
detected.
None of the problems below have any functional effect, they're just things
that are likely mistakes and are probably worth correcting.
If desired,
There is a "sage" source package, which builds the library packages
libsage2 and libsage-dev. In theory, I could try to be sneaky and take
"sage" as the binary package with "sagemath" as the source package name,
but I suspect I would not get away with it.
-Tim Abbott
On Sun, 20 Jul 2
The first bunch of SAGE dependencies entered the Debian NEW queue (the
queue of packages waiting for review from the Debian ftpmasters before
they are uploaded to Debian unstable) tonight; by tomorrow I expect that
that the remaining SAGE dependencies will enter the Debian NEW queue.
I am thus
When I try to connect to http://wiki.sagemath.org/ from various IP
addresses, I get the following error:
"Warning: You triggered the wiki's surge protection by doing too many
requests in a short time. Please make a short break reading the stuff you
already got. When you restart doing requests
I'm working on getting several of the SAGE dependencies not already in
Debian maintained in the main Debian archive. I had a few questions about
the future of some spkgs:
I've heard rumor that linbox_wrap might be being merged into mainline
linbox at some time in the near future. If this is
I attempted to build the 3.0.1alpha1 packages for Debian, but it doesn't
build, apparently due to some type errors. The build log is attached --
I'd appreciate any guesses as to what's going on here.
-Tim Abbott
--~--~-~--~~~---~--~~
To post to this group
I seem to have two major problems with my SAGE 3.0alpha6 Debian packages.
One seems to be difficulty finding the expanded executable for singular,
and the other seems to be a double free somewhere in linbox.
Do either of these sound familiar?
-Tim Abbott
// ***dError: Bug reported: Co
Hello,
I'm working on building SAGE 3.0 for Debian, but ran into a cython problem
(error message below):
I'm guessing the problem is Debian has cython 0.9.6.12 and I need running
0.9.6.13.1. Confirmation of this would be useful.
-Tim Abbott
Building sage/misc/cython_c.c because it
Since the Debian distribution of SAGE uses Maxima with GCL list, I figured
I'd run the benchmarks Mike posted on my installation. The SAGE times are
comparable to those in Mike's test, while the Maxima tests are faster:
sage: load /home/tabbott/fermat_gcd_1var.py
sage: time a = p1.gcd(p2, algo
, -1, 1, 1], [0, -1, 1, 2], [0, -1, 1,
3], [0, -1, 1, 4], [0, -1, 1, 5], [0, -1, 1, 6], [0, -1, 1, 7], [0, -1, 1,
8], [0, -1, 1, 9], [0, -1, 1, 10]]
**
Any ideas?
-Tim Abbott
On Sun, 30 Mar 2008, Timothy G Abbott wrot
hat are currently running.
I think the type (2) errors are bugs in the doctests (it's certainly a bad
documentation example if it only works from that directory), and once my
current doctest run finishes I'll submit patches for them.
-Tim Abbott
On Sun, 30 Mar 2008, mabs
In running doctests with my Debian installation of SAGE (where SAGE_ROOT
is set to /usr/lib/sagemath), it's been annoying that one needs to run the
tests as root so that SAGE can write to
- $SAGE_ROOT/tmp/test.log
- .doctest_filename.py in various directories of the SAGE install
- the directory
The set of Debian packages for SAGE 2.10.4 that I just announced do not
pass all doctests. Some known problems include:
- the scipy_sandbox is not installed (so delaunay.py won't load)
- jmol is not installed
- a few GAP packages are not available in Debian's GAP.
- PARI in Debian has the ma
I'm pleased to announce the availability of a working set of Debian
packages for SAGE 2.10.4. The dependencies of SAGE that are not already
in Debian have their own Debian packages that install into /usr, and the
SAGE package is uses these separately packaged dependencies (SAGE itself
lives i
19 matches
Mail list logo
