Would whomever has access to the skynet buildbot please
clean up the files it is generating?
Disk space on skynet is at a dangerous 97% full. The
buildbot seems to be the biggest disk hog:
2007 101G
2008 104G
2009 136G
Mariah Lenox
skynet system administrator
--
To post to
It looks like the bottom of
http://wiki.sagemath.org/devel/UsefulSoftware
has been spammed.
Mariah
--
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 g
The spkg r-2.10.1 includes inside it the spkg rpy2-2.0.8.
According to the relevant SPKG.txt, r-2.10.1 comes from
http://www.r-project.org/, while rpy2-2.0.8 comes from
http://rpy.sourceforge.net/rpy2.html.
Is it policy to put a sage package inside another sage
package ... or would it be better t
trac #2048 while humorous could be closed
Mariah
--
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: h
I believe ticket #5238 can be closed.
Ticket #5238 (remove qsieve.spkg and replace it by mpQS (part of FLINT))
should be closed because qsieve.spkg is no longer part of standard.
Would someone with the proper authority please
close #5238.
Mariah
--
To post to this group, send an email to sage-
I believe ticket #8700 (needs_review defect)
can be closed. It has a milestone of 4.4.4
and a patched spkg
libpng-1.2.35.p1.spkg
but libpng-1.2.35.p1.spkg is already
in 4.4.3 (and the problem mentioned in #8700
is fixed).
Can someone with the proper authority please
close #8700.
Mariah
--
Sage Developers,
trac # 4644 has a patch that I wrote to deal with
several problems with 'sage -sh'. It is listed
as fixed in 4.2.
Yet sage-4.2.1 does not seem to have the patch.
Did I miss a discussion about this issue that caused
my patch to be reverted?
--
Mariah
--
To post to this group
The open trac tickets #4644 and #5507 discuss
problems with "sage -sh", specifically
#4644 - No new prompt when doing a ./sage -sh
#5507 - $ sage -sh -c "echo hi there" # does not work, but should
$ sage -sh -c -c "echo hi there" # works, but shouldn't
There is also a problem th
