On Wed, Apr 16, 2014 at 5:52 PM, kcrisman wrote:
>
>
> On Wednesday, April 16, 2014 5:54:57 AM UTC-4, P Purkayastha wrote:
>>
>> Yes. There was some discussion about this in either sage-devel or
>> sage-notebook.
>>
>> On Apr 16, 2014 5:49 PM, "mmarco" wrote:
>>>
>>> So, what is the plan for the
On Wednesday, April 16, 2014 5:54:57 AM UTC-4, P Purkayastha wrote:
>
> Yes. There was some discussion about this in either sage-devel or
> sage-notebook.
> On Apr 16, 2014 5:49 PM, "mmarco" > wrote:
>
>> So, what is the plan for the future? Switch from the current notebook to
>> something li
On Wednesday, 16 April 2014 14:03:37 UTC-6, John H Palmieri wrote:
>
> Maybe instead just change the sage-spkg script:
>
>
> diff --git a/src/bin/sage-spkg b/src/bin/sage-spkg
> index b55867a..d77401a 100755
> --- a/src/bin/sage-spkg
> +++ b/src/bin/sage-spkg
> @@ -501,7 +501,7 @@ fi
> # Uncompres
Maybe instead just change the sage-spkg script:
diff --git a/src/bin/sage-spkg b/src/bin/sage-spkg
index b55867a..d77401a 100755
--- a/src/bin/sage-spkg
+++ b/src/bin/sage-spkg
@@ -501,7 +501,7 @@ fi
# Uncompresses a spkg to stdout.
uncompress_spkg()
{
-bzip2 -d -c "$1" 2>/dev/null || gzip
Hello,
How about shipping lbzip2 instead of bzip2? Or at least not building bzip2
if there is already one system-wide, so that it can be replaced with a
threaded version? (Were there issues with system bzip2?)
It is most noticeable on the huge polytope database, but will be also
useful for oth
Great! Thanks.
2014-04-16 19:50 UTC+02:00, Keith Clawson :
> I believe I fixed the problem, let me know if it happens again.
>
> -Keith
>
> On Wednesday, April 16, 2014 4:05:54 AM UTC-7, William wrote:
>>
>>
>> On Apr 16, 2014 2:19 AM, "Volker Braun" >
>>
>> wrote:
>> >
>> > I just visited the new
I believe I fixed the problem, let me know if it happens again.
-Keith
On Wednesday, April 16, 2014 4:05:54 AM UTC-7, William wrote:
>
>
> On Apr 16, 2014 2:19 AM, "Volker Braun" >
> wrote:
> >
> > I just visited the new wiki for the first time and got the "Surge
> protection warning". Maybe th
On Apr 16, 2014 2:19 AM, "Volker Braun" wrote:
>
> I just visited the new wiki for the first time and got the "Surge
protection warning". Maybe there is a reverse proxy in front that makes it
all appear to come from one IP? ;)
>
>
Yep - there is a proxy in front. But that is very temporary.
>
> O
Yes. There was some discussion about this in either sage-devel or
sage-notebook.
On Apr 16, 2014 5:49 PM, "mmarco" wrote:
> So, what is the plan for the future? Switch from the current notebook to
> something like the cloud interface? Will William release that part under
> the GPL?
>
> El miérco
So, what is the plan for the future? Switch from the current notebook to
something like the cloud interface? Will William release that part under
the GPL?
El miércoles, 16 de abril de 2014 10:24:29 UTC+2, P Purkayastha escribió:
>
> Some of these concerns are already addressed in cloud.sagemath
I just visited the new wiki for the first time and got the "Surge
protection warning". Maybe there is a reverse proxy in front that makes it
all appear to come from one IP? ;)
On Wednesday, April 16, 2014 6:15:57 AM UTC+1, vdelecroix wrote:
>
> Got a problem, do not know if it is because of m
Some of these concerns are already addressed in cloud.sagemath. The current
notebook is very much in maintenance stage at present.
On Tuesday, April 15, 2014 8:50:04 PM UTC+8, Jori Mantysalo wrote:
>
> On Tue, 15 Apr 2014, John Cremona wrote:
>
> > One thing you can do is run top on your server
12 matches
Mail list logo
