Trac is up and running on the new server. Let me know if anything doesn't
work.
-Keith
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@goo
Log ends with "Successfully installed atlas-3.10.1.p6" ;-)
On Sunday, October 13, 2013 1:11:44 AM UTC+1, Dr David Kirkby wrote:
>
> It failed again. I've not looked at the reason, and in any case you
> know more how to understand this than me. But I've attached the log.
> I'm guessing this log
I will be suspending Trac at 9:00 PM Pacific time today in order to move it
to a new server. The work should be done in 15-30 minutes, and I'll post
another notice to the group as soon as it's back online. I'm also doubling
the number of CPUs, increasing the RAM, and making various configuration
The new ticket page is working for me right now. Trac is experiencing a
heavy load today and there have been some transient problems like this. I
have prepared a new VM with twice as many CPUs, more memory, and some
software optimizations that should help stabilize Trac on these busy days.
I'm
I just tried creating a new ticket on trac and got an error:
Internal Server Error
The server encountered an internal error or misconfiguration and was
unable to complete your request.
Please contact the server administrator, [no address given] and inform
them of the time the error occurred
On Sat, Oct 12, 2013 at 4:02 AM, Thierry
wrote:
> On Fri, Oct 11, 2013 at 06:08:15AM -0700, William Stein wrote:
>> On Oct 11, 2013 12:00 AM, "Jeroen Demeyer" wrote:
>> > Should we mention in the Sage manual (for example, here:
>> http://www.sagemath.org/doc/installation/quick-guide.html) that it
>> http://voice.instructure.com/blog/bid/148942/Our-Open-Source-Strategy
> >>
> >> Interesting points, and of course the question of whether it stays open
> >> remains...
> >
> >
>
>
> It's AGPL, according to
>
> >> If you haven't been following the LMS scene for a while, a new AGPL
>>
The invalid assembler is normal, ATLAS has various implementations and it
tries to compile them all (and then time the ones where compilations
succeeds).
I had a mistake in the spkg, updated version is again here:
http://boxen.math.washington.edu/home/vbraun/spkg/atlas-3.10.1.p6.spkg
On Satu
On Fri, Oct 11, 2013 at 06:08:15AM -0700, William Stein wrote:
> On Oct 11, 2013 12:00 AM, "Jeroen Demeyer" wrote:
> > Should we mention in the Sage manual (for example, here:
> http://www.sagemath.org/doc/installation/quick-guide.html) that it is
> entirely possible to run Sage without actually i
FWIW, let me try to explain some background.
The PIL package build system checks for various alternatives (build with or
without Tcl/TK support, build with our without jpeg support, etc.), but
does that in a highly selfmade way, which not always works.
Sage does not need PIL to be built with jpe
Le 11/10/2013 13:45, Tharindu Rusira a écrit :
> Hi,
> I'm using sage 5.11 (built from developer source code). I have written
> some python scripts that I want to call within sage.
>
> I copied my source files into my sage path but when I call
> /sage:load("file_name.py")/ sage fails to find some
11 matches
Mail list logo
