On Feb 6, 2008 3:24 PM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
> Sorry for being late to this thread, but I think we should continue in
> place upgrades. All the issues that pop up are issues that we need to
> solve and while it can be taxing on our resources these bugs will be
> exposed either way
Sorry for being late to this thread, but I think we should continue in
place upgrades. All the issues that pop up are issues that we need to
solve and while it can be taxing on our resources these bugs will be
exposed either way. As Sage branches out from its core group of users
which are probably
On Feb 5, 4:41 pm, Burcin Erocal <[EMAIL PROTECTED]> wrote:
> On Tue, 05 Feb 2008 09:06:57 -0600
>
>
>
> Jason Grout <[EMAIL PROTECTED]> wrote:
> > Burcin Erocal wrote:
>
> > Can we add the tuning information extraction to the spkg script or
> > somewhere that we can just type one command in (s
-- Forwarded message --
From: Iftikhar Burhanuddin <[EMAIL PROTECTED]>
Date: Feb 6, 2008 3:00 PM
Subject: Tomorrow's talks
To: [EMAIL PROTECTED]
Cc: Iftikhar Burhanuddin <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
Craig Citro <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
William [cc: Alex,
Brian Lauber wrote:
> Hi Michael.
Hi Brian,
> I was looking at the Trac page for SAGE and noticed that
> you are doing a little work with SELinux. I'm actually planning on
> building some custom SELinux policies for SAGE in the next two weeks,
> and I don't want to step on your toes in the proc
Craig thanks very much for the suggestions:
> $ sage -sh
> $ cd $SAGE_ROOT
> $ echo '/' >local/lib/sage-current-location.txt
> $ cd local/bin
> $ ./sage-location
I tried this but still ended up with the same error (with the odd page
component /Users/was/build/...), so I ended up doing a fresh
in
