[sage-devel] Re: Several years of bug reports

2013-12-10 Thread P Purkayastha

On 12/10/2013 11:08 PM, Harald Schilly wrote:

On Tue, Dec 10, 2013 at 3:55 PM, kcrisman  wrote:

This is a very good idea. Then the notebook doesn't need to be changed.



+1


The 301 redirect works now:
http://sagemath.org/report-issue

Harald



Thanks. I have put up a pull request:
https://github.com/sagemath/sagenb/pull/186

--
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...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [sage-devel] Re: Several years of bug reports

2013-12-10 Thread Harald Schilly
On Tue, Dec 10, 2013 at 3:55 PM, kcrisman  wrote:
>> This is a very good idea. Then the notebook doesn't need to be changed.
>
>
> +1

The 301 redirect works now:
http://sagemath.org/report-issue

Harald

-- 
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...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.


[sage-devel] Re: Several years of bug reports

2013-12-10 Thread kcrisman


On Monday, December 9, 2013 8:43:09 PM UTC-5, P Purkayastha wrote:
>
> On 12/10/2013 02:15 AM, Harald Schilly wrote: 
> > additional idea: we should change the URL to an indirect one. Then we 
> > can change this more easily! e.g. "http://sagemath.org/report-issue"; 
> > which is a 301 redirect to ask or whatever we want. 
>
> This is a very good idea. Then the notebook doesn't need to be changed. 
>

+1 

-- 
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...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [sage-devel] Help in creating trac accounts.

2013-12-10 Thread Kannappan Sampath
I'd be willing to help with this task although I must confess I have not
been actively involved in Sage development lately, but then, I am now
beginning to undertake some development work.

With Sincere Regards,
Kannappan.


On Tue, Dec 10, 2013 at 7:41 PM, Maarten Derickx <
m.derickx.stud...@gmail.com> wrote:

> Dear All,
>
> As most of you probably know, there is a mailinglist 
> sage-trac-account.
> The purpose for this mailinglist is to distribute the task of creating trac
> accounts among several sage devs, so that people needing a trac account wil
> receive one in a timely fashion. However the number of people actively
> creating accounts has dropped, causing potential new sage devs to get their
> trac accounts later then desired. So I'm now asking if there are people
> that would like to help by creating an account say once a week (takes about
> 5 min).
>
> The reason the creation process is manual is because the captcha of trac
> is not strong enough so our trac server will get spammed with useless
> messages about certain medicines if we made the process automatic as used
> to happen in the past.
>
> If you are interested in helping out please send a message either to me or
> to the sage-trac-account mailinglist.
>
> Thanks,
> Maarten
>
> --
> 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...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [sage-devel] Re: computing a graph diameter

2013-12-10 Thread Nathann Cohen
Yooo !!

Ahahaha. Okay okay. Well, then tell me when you feel sufficiently at ease 
> with git to review patches, and you'll have that patch two hours from then 
> :-D
>

Okay, even though I didn't hear anything from you since, the ticket is 
there and ready : http://trac.sagemath.org/ticket/15507

Nathann 

-- 
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...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.


[sage-devel] Help in creating trac accounts.

2013-12-10 Thread Maarten Derickx
Dear All,

As most of you probably know, there is a mailinglist 
sage-trac-account. 
The purpose for this mailinglist is to distribute the task of creating trac 
accounts among several sage devs, so that people needing a trac account wil 
receive one in a timely fashion. However the number of people actively 
creating accounts has dropped, causing potential new sage devs to get their 
trac accounts later then desired. So I'm now asking if there are people 
that would like to help by creating an account say once a week (takes about 
5 min).

The reason the creation process is manual is because the captcha of trac is 
not strong enough so our trac server will get spammed with useless messages 
about certain medicines if we made the process automatic as used to happen 
in the past.

If you are interested in helping out please send a message either to me or 
to the sage-trac-account mailinglist.

Thanks,
Maarten

-- 
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...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [sage-devel] Flint-2.3.pl.spkg failed installation from source on openSuse 12.2 64-bit intel i5

2013-12-10 Thread Jeroen Demeyer

On 2013-12-10 12:21, Volker Braun wrote:

The only thing that I can think of is that the second time we install
mpc (not in the compiler bootstrap) there is a short window where the
compiler won't work as libmpc is being modified.

We fixed that in #14168.

--
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...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.


[sage-devel] Re: GAP3

2013-12-10 Thread arcisd
Hello, sorry, it is, thank you:

gap-3.4.4.p0

Extracting package /home/arcis/Programs/4/gap-3.4.4.p0.spkg
-rw-rw-r-- 1 arcis arcis 38637526 Dec  9 09:23 
/home/arcis/Programs/4/gap-3.4.4.p0.spkg
Finished extraction

Host system:
Linux T3600-Doctorant-Arcis 3.2.0-57-generic #87-Ubuntu SMP Tue Nov 12 
21:35:10 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/home/arcis/Programs/sage-5.12/local/libexec/gcc/x86_64-unknown-linux-gnu/4.7.3/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../src/configure 
--prefix=/home/arcis/Programs/sage-5.12/local 
--with-local-prefix=/home/arcis/Programs/sage-5.12/local 
--with-gmp=/home/arcis/Programs/sage-5.12/local 
--with-mpfr=/home/arcis/Programs/sage-5.12/local 
--with-mpc=/home/arcis/Programs/sage-5.12/local --with-system-zlib 
--disable-multilib --disable-nls  
Thread model: posix
gcc version 4.7.3 (GCC) 

Compiling target ibm-i386-linux-gcc-optimized
make[1]: Entering directory 
`/home/arcis/Programs/sage-5.12/spkg/build/gap-3.4.4.p0/src/src'
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O2 -DSYS_IS_USG -DSYS_HAS_TIME_PROTO -DSYS_HAS_SIGNAL_PROTO 
-DSYS_HAS_IOCTL_PROTO   -c -o system.o system.c
make[1]: Leaving directory 
`/home/arcis/Programs/sage-5.12/spkg/build/gap-3.4.4.p0/src/src'
make[1]: Entering directory 
`/home/arcis/Programs/sage-5.12/spkg/build/gap-3.4.4.p0/src/src'
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o gap.o gap.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o gasman.o gasman.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o scanner.o scanner.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o idents.o idents.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o read.o read.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o eval.o eval.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o integer.o integer.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o rational.o rational.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o cyclotom.o cyclotom.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o unknown.o unknown.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o finfield.o finfield.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o polynom.o polynom.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o permutat.o permutat.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o word.o word.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o costab.o costab.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o tietze.o tietze.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o agcollec.o agcollec.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o aggroup.o aggroup.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o pcpresen.o pcpresen.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o list.o list.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o plist.o plist.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o set.o set.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o vector.o vector.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o vecffe.o vecffe.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o range.o range.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o blister.o blister.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o string.o string.c
gcc -m32 -O3 -fomit-frame-pointer -pipe -fno-strength-reduce -march=i686 
-DCPU=686 -g -O3   -c -o record.o record.c
gcc -m32 -O3 -fomit-frame-po

Re: [sage-devel] Flint-2.3.pl.spkg failed installation from source on openSuse 12.2 64-bit intel i5

2013-12-10 Thread Volker Braun
The only thing that I can think of is that the second time we install mpc 
(not in the compiler bootstrap) there is a short window where the compiler 
won't work as libmpc is being modified. If that is the case then a 
recompile should work. 

On Tuesday, December 10, 2013 7:36:17 AM UTC, Jeroen Demeyer wrote:
>
> That's an error I cannot explain. Can you send the *whole* 
> logs/install.log file please, so we can better diagnose the problem. 
>
>

-- 
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...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.


[sage-devel] Re: OS X buildbots

2013-12-10 Thread Volker Braun
I bought a maxed out mac mini to run as a OSX 10.9 buildbot. It should 
arrive before xmas, I hope ;-)


On Tuesday, December 10, 2013 7:30:02 AM UTC, Jeroen Demeyer wrote:
>
> Let me ask again for OS X buildbots. We currently only have OS X 10.4 
> PPC and OS X 10.6 x86_64 buildbots and it would be good to have some 
> more recent ones as well. Anyone has a spare OS X server sitting around? . 
>

-- 
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...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.