[sage-devel] Re: Reviewing package version updates (in particular, gap)

[Andrey Novoseltsev]

On Tuesday, 24 December 2013 16:01:00 UTC-7, Volker Braun wrote:
>
> The current process of updating third-party packages is broken:
>
> a) There isn't really anything to review beyond running it on the buildbot
> b) Nobody dares to press the "positive review" button
> c) Frustation to see your work waste away on trac
>
> for example, out of the last three Gap package updates that I packaged 
> only one was ever looked at. So I'm proposing that I'll just merge package 
> updates if they *work* as long as there isn't too much wonkyness introduced 
> into the build script. If you have any opinion on that, please post in this 
> thread :-)
>
> [ ]  Yes, go ahead
> [ ]  No, I want to volunteer as the reviewer for package upgrades
>
> See also: http://trac.sagemath.org/15582
>

How about a slight twist on the first option:

[X] Have a whitelist of developers who are allowed to post an updated 
package and set them to positive review immediately (listing themselves as 
reviewers) because they judge the update to be trivial and in no need of 
discussion

It is one thing to blindly trust Volker Braun's GAP update, but that fresh 
gcc-5.3 package from Folker Brown looks suspicious...

-- 
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: "git trac" command

[Andrey Novoseltsev]

On Wednesday, 25 December 2013 15:01:03 UTC-7, Nathann Cohen wrote:
>
> Well, if you tried it a lot already, I don't see what's the problem. 
> Plus I can swear I would use it too, and other probably too. Actually, 
> with this kind of thing around I'm pretty sure no developper would use 
> the dev scripts anymore :-P 
>
> Nathann 
>

I am not sure about all developers, but I certainly would prefer to learn 
"real git" instead of custom scripts. Having something to automatically 
take care of ticket numbers and getting/setting/pushing appropriate 
branches would be really nice, I was always annoyed by keeping track of 
which patch goes where and which still has to have ticket added in the 
name/comment.

I don't care if it is a package or not as I am not likely to modify these 
scripts, but I definitely want them available without extra steps!

Andrey

-- 
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] Reviewing package version updates (in particular, gap)

[Francois Bissey]

Yes it is. But it is not in:
http://trac.sagemath.org/wiki/TicketReports
or 
http://trac.sagemath.org/report
If there is an easy of collecting those tickets please educate me!

François

From: sage-devel@googlegroups.com [sage-devel@googlegroups.com] on behalf of 
Travis Scrimshaw [tsc...@ucdavis.edu]
Sent: Thursday, 26 December 2013 11:43
To: sage-devel@googlegroups.com
Subject: Re: [sage-devel] Reviewing package version updates (in particular, gap)

Isn't that what the "packages: *" components are for?

On Wednesday, December 25, 2013 10:49:44 AM UTC-8, Jean-Pierre Flori wrote:


On Wednesday, December 25, 2013 7:45:05 PM UTC+1, François wrote:
Going back to the general subject. Could we have a shortcut on the ticket 
report page
grabbing update/upgrade of packages. Unless the potential reviewer(s) are cc 
automatically
that would any review easier, as in more easy to find.

Grep update or upgrade in the ticket title?

--
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.
This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.

Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.

-- 
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: "git trac" command

[Travis Scrimshaw]

PS - Or as an optional spkg.

-- 
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: "git trac" command

[Travis Scrimshaw]

Maybe I'm not getting something, but it seems like a thin layer over git 
which just transforms ticket numbers into their proper git branches. For 
me, I'm finding using a combination of git via the terminal and trac open 
on my webbrowser works well, but I'm fine using alt-tab between windows and 
don't have my terminal taking up the whole screen... On that basis, I think 
you should make them available, but not included with Sage (perhaps on trac 
or the sagemath.org page).

Best,
Travis


On Wednesday, December 25, 2013 12:36:45 PM UTC-8, Volker Braun wrote:
>
> I've been working on a "git trac" subcommand to complement the git suite 
> with trac integration instead of the separate UI that the sage -dev scripts 
> present. This project is the basis for my release management scripts, so I 
> have been eating my own dog food for a while now. I think it is now in a 
> state where it would be useful to others, so I propose to integrate it as a 
> standard spkg. Obligatory vote:
>
> [ ]  Yes, please
> [ ]  Make it optional
> [ ]  No, you stink
>
> http://trac.sagemath.org/ticket/15587
>
>
> Usage
> -
>
> * Print the trac ticket information using ``git trac get
>   ``. 
>
>   $ git trac get 12345
>   
> ==
>   Trac #12345: Title of ticket 12345
>   ...
>   
> ==
>
>   Alternatively, you can pass a remote branch name, in which case trac
>   is searched for a ticket whose (remote) "Branch:" field equals the
>   branch name.  If that fails, the ticket number will be deduced from
>   the branch name by scanning for a number. If you neither specify a
>   ticket number or branch name, the local git branch name is used:
>
>   $ git branch
>   /u/user/description
>   $ git trac get
>   
> ==
>   Trac #n: Title
>   
>   Description
>   Status: Status  Component: Component 
>
>   ...
>   Branch: u/user/description
>   
> ==
>
>
> * Checkout 
>   a remote branch:
>
>   $ git trac checkout 12345
>
>   Will automatically pick a local branch name ``t/12345/description``
>   based on the remote branch name. If you want a particular local
>   branch name, you can specify it manually:
>
>   $ git trac checkout -b my_brach 12345
>
>
> * Create a new ticket on trac, and a new local branch 
>   corresponding to it:
>
>   $ git trac create "This is the summary"
>
>   This will automatically create a local branch name
>   ``t/12345/this_is_the_summary``. You can specify it manually if you
>   prefer with:
>   
>   $ git trac create -b my_branch "This is the summary"
>
>
> * Pull (= fetch + merge) from the branch
>   on a ticket:
>
>   $ git trac pull 12345
>
>   You can omit the ticket number, in which case the script will try to
>   search for the ticket having the local branch name attached. If that
>   fails, an attempt is made to deduce the ticket number from the local
>   branch name.
>
>
> * Push (upload) to the branch
>   on a ticket, and set the trac "Branch:" field accordingly:
>
>   $ git trac push 12345
>
>   You can omit the ticket number, in which case the script will try to
>   search for the ticket having the local branch name attached. If that
>   fails, an attempt is made to deduce the ticket number from the local
>   branch name.
>
>
> * Log of the commits for a
>   ticket:
>
>   $ git trac log 12345
> 
>
> * Find the trac ticket for a 
>   commit, either identified by its SHA1 or branch/tag name.
>
>   $ git log --oneline -1 ee5e39e
>   ee5e39e Allow default arguments in closures
>   $ git trac find ee5e39e
>   Commit has been merged by the release manager into your current 
> branch.
>   commit 44efa774c5f991ea5f160646515cfe8d3f738479
>   Merge: 5fd5442 679310b
>   Author: Release Manager >
>   Date:   Sat Dec 21 01:16:56 2013 +
>
>   Trac #15447: implement evaluation of PARI closures
>
>
> Too Long, Didn't Read
> -
>
> To fix a bug, start with
>
> $ git trac create "Fix foo"
> 
> This will open the ticket and create a new local branch
> ``t//fix_foo``. Then edit Sage, followed by 
>
> $ git add 
> $ git commit
>
> Repeat edit/commit as necessary. When you are finished, run
>
> $ git trac push
>
> It will take the ticket number out of the branch name, so you don't
> have to specify it.
>
>

-- 
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 gro

Re: [sage-devel] Reviewing package version updates (in particular, gap)

[Travis Scrimshaw]

Isn't that what the "packages: *" components are for?

On Wednesday, December 25, 2013 10:49:44 AM UTC-8, Jean-Pierre Flori wrote:
>
>
>
> On Wednesday, December 25, 2013 7:45:05 PM UTC+1, François wrote:
>>
>> Going back to the general subject. Could we have a shortcut on the ticket 
>> report page 
>> grabbing update/upgrade of packages. Unless the potential reviewer(s) are 
>> cc automatically 
>> that would any review easier, as in more easy to find. 
>>
>> Grep update or upgrade in the ticket title? 
>

-- 
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: "git trac" command

[Georg S. Weber]

On Wednesday, 25 December 2013 21:36:45 UTC+1, Volker Braun wrote:
>
> I've been working on a "git trac" subcommand to complement the git suite 
> with trac integration instead of the separate UI that the sage -dev scripts 
> present. This project is the basis for my release management scripts, so I 
> have been eating my own dog food for a while now. I think it is now in a 
> state where it would be useful to others, so I propose to integrate it as a 
> standard spkg. Obligatory vote:
>
> [ X ]  Yes, please
> [ ]  Make it optional
> [ ]  No, you stink
>
> http://trac.sagemath.org/ticket/15587
>
>
>
IMHO, I wouldn't mind if this code would stay forever in a separate spkg. 
Maybe other projects than the Sage math community would find it useful.

After all, it's about enhancing the "git" command in conjunction with a 
"trac" installation to support a certain development/ticket workflow, which 
is agnostic to "Sage as a viable alternative to other math software"). 

-- 
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: "git trac" command

[Nathann Cohen]

> In that case the script will find the first merge that is made by "Release
> Manager", which is #14480
>
> For really old commits we have no way to associate the trac ticket.

Okayokay I see, I was just being curious :-)

Then I'd personally vote for "inclusion into Sage, without making it a
SPKG". It's like I can't agree with anybody, nowadays... :-P

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.

Re: [sage-devel] Re: "git trac" command

[Volker Braun]

On Wednesday, December 25, 2013 10:01:03 PM UTC, Nathann Cohen wrote:
>
> Nono, I meant : does it work if the commit *was* merged, but was 
> merged years ago. 


In that case the script will find the first merge that is made by "Release 
Manager", which is #14480

For really old commits we have no way to associate the trac ticket.

For not quite so old commits Jeroen started to enforce trac ticket numbers 
in the commit message. So in that case its obvious without the script.

-- 
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: "git trac" command

[Nathann Cohen]

Yooo !

> If its not merged then it is not clear which ticket it belongs to, if at all. 
> So thats a no. But then the real use case is that you have an already merged 
> commit (from git blame or git log) and you want to know the ticket.

Nono, I meant : does it work if the commit *was* merged, but was
merged years ago. When you have no way to be sure that the message of
the merge commit respected a specific strandard.

> I don't mind integrating it in Sage but at least during the transition period 
> thats a bad design choice imho.

HMm O_o

Well, if you tried it a lot already, I don't see what's the problem.
Plus I can swear I would use it too, and other probably too. Actually,
with this kind of thing around I'm pretty sure no developper would use
the dev scripts anymore :-P

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] Re: "git trac" command

[Volker Braun]

On Wednesday, December 25, 2013 9:37:53 PM UTC, Nathann Cohen wrote:
>
> Does the "find ticket from hash" feature works for tickets that were not 
> merged as Git tickets too ?
>

If its not merged then it is not clear which ticket it belongs to, if at 
all. So thats a no. But then the real use case is that you have an already 
merged commit (from git blame or git log) and you want to know the ticket.

I don't mind integrating it in Sage but at least during the transition 
period thats a bad design choice imho.

-- 
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: Re: [sage-devel] The Annual Sage on Python 3 Thread

[Jean-Pierre Flori]

On Wednesday, December 25, 2013 8:40:27 PM UTC+1, Jean-Pierre Flori wrote:
>
> On a slightly unrelated topic, currently the only function of pycrypto 
> used in the Sage library is indeed in the monoid stuff and that's the 
> byte_to_long function.
> Although I don't feel we should remove pycrypto from standard packages, I 
> feel we could implement this ourselves if this prevents a boring warning 
> from breaking tests (see #14854).
>
Anyway, I've completely disabled any call to pycrypto in the monoid stuff.
Feel free to review http://trac.sagemath.org/ticket/14854
The topic of removing, making optional or whatever with pycrypto can be 
dealt independently of that. 

-- 
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: "git trac" command

[Nathann Cohen]

Hey, after re-thinking it I'm not sure anymore. Why do you want to make it
a spkg and not let it be part of Sage ?

The problem with it being a spkg is that *you* are upstream, and so you are
the only one able to make changes to it.

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] Re: 404 on Sage Developer Conventions

[Nathann Cohen]

Wooh !! No rules !! I'll be reviewing my own tickets in a second 
:-PPP

Nathann

On Wednesday, December 25, 2013 4:32:22 PM UTC+1, Darij Grinberg wrote:
>
> Hi guys, 
>
> this site is now 404: 
> http://www.sagemath.org/doc/developer/conventions.html 
> Where has it moved? 
>
>   Best regards, 
>   Darij 
>

-- 
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: "git trac" command

[Nathann Cohen]

I was personally thinking of writing some bash scripts to do the same so I 
am all for it :-P

Does the "find ticket from hash" feature works for tickets that were not 
merged as Git tickets too ?

Nathann

On Wednesday, December 25, 2013 9:36:45 PM UTC+1, Volker Braun wrote:
>
> I've been working on a "git trac" subcommand to complement the git suite 
> with trac integration instead of the separate UI that the sage -dev scripts 
> present. This project is the basis for my release management scripts, so I 
> have been eating my own dog food for a while now. I think it is now in a 
> state where it would be useful to others, so I propose to integrate it as a 
> standard spkg. Obligatory vote:
>
> [ ]  Yes, please
> [ ]  Make it optional
> [ ]  No, you stink
>
> http://trac.sagemath.org/ticket/15587
>
>
> Usage
> -
>
> * Print the trac ticket information using ``git trac get
>   ``. 
>
>   $ git trac get 12345
>   
> ==
>   Trac #12345: Title of ticket 12345
>   ...
>   
> ==
>
>   Alternatively, you can pass a remote branch name, in which case trac
>   is searched for a ticket whose (remote) "Branch:" field equals the
>   branch name.  If that fails, the ticket number will be deduced from
>   the branch name by scanning for a number. If you neither specify a
>   ticket number or branch name, the local git branch name is used:
>
>   $ git branch
>   /u/user/description
>   $ git trac get
>   
> ==
>   Trac #n: Title
>   
>   Description
>   Status: Status  Component: Component 
>
>   ...
>   Branch: u/user/description
>   
> ==
>
>
> * Checkout 
>   a remote branch:
>
>   $ git trac checkout 12345
>
>   Will automatically pick a local branch name ``t/12345/description``
>   based on the remote branch name. If you want a particular local
>   branch name, you can specify it manually:
>
>   $ git trac checkout -b my_brach 12345
>
>
> * Create a new ticket on trac, and a new local branch 
>   corresponding to it:
>
>   $ git trac create "This is the summary"
>
>   This will automatically create a local branch name
>   ``t/12345/this_is_the_summary``. You can specify it manually if you
>   prefer with:
>   
>   $ git trac create -b my_branch "This is the summary"
>
>
> * Pull (= fetch + merge) from the branch
>   on a ticket:
>
>   $ git trac pull 12345
>
>   You can omit the ticket number, in which case the script will try to
>   search for the ticket having the local branch name attached. If that
>   fails, an attempt is made to deduce the ticket number from the local
>   branch name.
>
>
> * Push (upload) to the branch
>   on a ticket, and set the trac "Branch:" field accordingly:
>
>   $ git trac push 12345
>
>   You can omit the ticket number, in which case the script will try to
>   search for the ticket having the local branch name attached. If that
>   fails, an attempt is made to deduce the ticket number from the local
>   branch name.
>
>
> * Log of the commits for a
>   ticket:
>
>   $ git trac log 12345
> 
>
> * Find the trac ticket for a 
>   commit, either identified by its SHA1 or branch/tag name.
>
>   $ git log --oneline -1 ee5e39e
>   ee5e39e Allow default arguments in closures
>   $ git trac find ee5e39e
>   Commit has been merged by the release manager into your current 
> branch.
>   commit 44efa774c5f991ea5f160646515cfe8d3f738479
>   Merge: 5fd5442 679310b
>   Author: Release Manager >
>   Date:   Sat Dec 21 01:16:56 2013 +
>
>   Trac #15447: implement evaluation of PARI closures
>
>
> Too Long, Didn't Read
> -
>
> To fix a bug, start with
>
> $ git trac create "Fix foo"
> 
> This will open the ticket and create a new local branch
> ``t//fix_foo``. Then edit Sage, followed by 
>
> $ git add 
> $ git commit
>
> Repeat edit/commit as necessary. When you are finished, run
>
> $ git trac push
>
> It will take the ticket number out of the branch name, so you don't
> have to specify it.
>
>

-- 
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: sage -upgrade idiosyncracies

[Volker Braun]

Do a "make distclean" to rebuild from scratch. I'm pretty sure that the 
post-6.0 scripts will copy updates to local as required. Let us know if you 
see this behavior again...


On Wednesday, December 25, 2013 5:33:39 PM UTC, P Purkayastha wrote:
>
> Yes. 
>
> The output of make (run again; nothing to update) is attached. There are 
> no differences between github, trac and my local develop branch. 
>
> ~/Installations/sage» git rev-parse --abbrev-ref HEAD 
> develop 
> ~/Installations/sage» git diff develop origin/develop 
> ~/Installations/sage» diff -q local/bin/sage-upgrade src/bin/sage-upgrade 
> Files local/bin/sage-upgrade and src/bin/sage-upgrade differ 
> ~/Installations/sage [1] »  git diff develop trac/develop 
> ~/Installations/sage» 
>
> On 12/26/2013 12:32 AM, Volker Braun wrote: 
> > You need to run "make" to install the updated scripts in local/, did you 
> > do that? 
> > 
> > On Wednesday, December 25, 2013 4:21:51 PM UTC, P Purkayastha wrote: 
> > 
> > Well, that's the problem. local/bin is not tracked by git. And I am 
> not 
> > sure how else I can force the upgrade of the scripts. In terms of 
> the 
> > sage library, I am already on sage-6.1.beta2. 
> > 
> > On 12/26/2013 12:12 AM, Volker Braun wrote: 
> >  > It seems your first installation is pre-6.0. Before that was 
> > released 
> >  > there were bugs in the upgrade script. Use git to manually 
> > upgrade to 
> >  > 6.0 first, then "sage -upgrade" will (should) work. 
> >  > 
> >  > 
> >  > On Wednesday, December 25, 2013 2:22:43 PM UTC, P Purkayastha 
> wrote: 
> >  > 
> >  > With the second method it is all very smooth. I did a 
> >  > .../src/sage/sage-6.0.server> git fetch origin 
> >  > 
> >  > 
> >  > The fetch is also performed by the upgrade script, no need to do 
> it 
> >  > manually. 
> >  > 
> >  > followed by 
> >  > .../src/sage/sage-6.0.server> ./sage -upgrade develop 
> >  > 
> >  > 
> >  > -- 
> >  > You received this message because you are subscribed to the 
> Google 
> >  > Groups "sage-git" group. 
> >  > To unsubscribe from this group and stop receiving emails from it, 
> > send 
> >  > an email to sage-git+u...@googlegroups.com . 
> >  > For more options, visit https://groups.google.com/groups/opt_out 
> > . 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> > Groups "sage-git" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> > an email to sage-git+u...@googlegroups.com . 
> > 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] building sage 6.0 on debian live (squeeze)

[Thierry]

Hi,

On Mon, Dec 23, 2013 at 02:07:12PM -0800, Emil Widmann wrote:
> I am trying to build the latest sage release with the possible goal of 
> releasing another Live image version (USB/CD/HD disk image).

i am maintaining a Debian live version of Sage for more than one year, so
we can join our efforts and mutualize our ideas!

http://sagedebianlive.metelu.net/

The source code of the customization and build scripts is (GPL) available
here, so there is room for collective developpment (still using mercurial
though ;) http://sagedebianlive.metelu.net/sources/sagedebianlive/

Also, there are some tools that make the current Sage Debian live
different from a raw debian live in order to fit to our particular needs,
some details on the design are available here:
http://www.lirmm.fr/~monteil/papiers/fichiers/Monteil-Slides-Extremecom2013.pdf
http://www.lirmm.fr/~monteil/papiers/fichiers/Monteil-USB.pdf

In particular:
- i am using a different persistence scheme than the classical use of a
  separate ext2 partition in order to ease the use for windoz users (this
  OS refuses to read ext2 filesystems).
- unlike Puppy, Debian live does not offers an easy tool to change the
  system language, hence i had ot write one.
- there is an easy clone/upgrade script that allows to spread the USB key
  very easily and fast in a classroom/workshop, and replaces the
  download/burn by a key2key propagation (allowing content sharing between
  peers (e.g. worksheets), while still preserving their private data).
- it is huge (e.g. it contains latex and some optional Sage spkg such as
  database_gap), to allow a remote user without a good internet connexion
  to experience an autonomous Linux system.
- if a computer BIOS can not boot from a USB key, there is a small
  kexec-based CD image that allows to boot on the USB keys (also works for
  Mac UEFI uncompatible boot system)
- i am currently writing an off-line integrity checking system (explained
  at the end of the slides).
- a raspberry pi can be used as a kiosk for automatic upgrade of keys
  (plug the target key to the pi and udev will launch a non-interactive
  upgrade script).

By the way, it could be interesting to put a link to this Sage Debian live
from the sagemath.org download page (the current link "live CD" points to
a 5.3 version of Sage).

Ciao,
Thierry


-- 
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] "git trac" command

[Volker Braun]

I've been working on a "git trac" subcommand to complement the git suite 
with trac integration instead of the separate UI that the sage -dev scripts 
present. This project is the basis for my release management scripts, so I 
have been eating my own dog food for a while now. I think it is now in a 
state where it would be useful to others, so I propose to integrate it as a 
standard spkg. Obligatory vote:

[ ]  Yes, please
[ ]  Make it optional
[ ]  No, you stink

http://trac.sagemath.org/ticket/15587


Usage
-

* Print the trac ticket information using ``git trac get
  ``. 

  $ git trac get 12345
  
==
  Trac #12345: Title of ticket 12345
  ...
  
==

  Alternatively, you can pass a remote branch name, in which case trac
  is searched for a ticket whose (remote) "Branch:" field equals the
  branch name.  If that fails, the ticket number will be deduced from
  the branch name by scanning for a number. If you neither specify a
  ticket number or branch name, the local git branch name is used:

  $ git branch
  /u/user/description
  $ git trac get
  
==
  Trac #n: Title
  
  Description
  Status: Status  Component: Component 
   
  ...
  Branch: u/user/description
  
==


* Checkout 
  a remote branch:

  $ git trac checkout 12345

  Will automatically pick a local branch name ``t/12345/description``
  based on the remote branch name. If you want a particular local
  branch name, you can specify it manually:

  $ git trac checkout -b my_brach 12345


* Create a new ticket on trac, and a new local branch 
  corresponding to it:

  $ git trac create "This is the summary"

  This will automatically create a local branch name
  ``t/12345/this_is_the_summary``. You can specify it manually if you
  prefer with:
  
  $ git trac create -b my_branch "This is the summary"


* Pull (= fetch + merge) from the branch
  on a ticket:

  $ git trac pull 12345

  You can omit the ticket number, in which case the script will try to
  search for the ticket having the local branch name attached. If that
  fails, an attempt is made to deduce the ticket number from the local
  branch name.


* Push (upload) to the branch
  on a ticket, and set the trac "Branch:" field accordingly:

  $ git trac push 12345

  You can omit the ticket number, in which case the script will try to
  search for the ticket having the local branch name attached. If that
  fails, an attempt is made to deduce the ticket number from the local
  branch name.


* Log of the commits for a
  ticket:

  $ git trac log 12345


* Find the trac ticket for a 
  commit, either identified by its SHA1 or branch/tag name.

  $ git log --oneline -1 ee5e39e
  ee5e39e Allow default arguments in closures
  $ git trac find ee5e39e
  Commit has been merged by the release manager into your current 
branch.
  commit 44efa774c5f991ea5f160646515cfe8d3f738479
  Merge: 5fd5442 679310b
  Author: Release Manager 
  Date:   Sat Dec 21 01:16:56 2013 +

  Trac #15447: implement evaluation of PARI closures


Too Long, Didn't Read
-

To fix a bug, start with

$ git trac create "Fix foo"

This will open the ticket and create a new local branch
``t//fix_foo``. Then edit Sage, followed by 

$ git add 
$ git commit

Repeat edit/commit as necessary. When you are finished, run

$ git trac push

It will take the ticket number out of the branch name, so you don't
have to specify it.

-- 
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: Re: [sage-devel] The Annual Sage on Python 3 Thread

[William Stein]

On Wed, Dec 25, 2013 at 11:46 AM, R. Andrew Ohana
 wrote:
> I disagree with the sentiment that we should make python package X a
> standard package because it is useful for Y. At that rate, every (compatibly
> licensed) mathematics and science python package will be a standard part of
> sage. Because pycrypto is not truly a dependency of the sage library (i.e.
> used in a non-trivial manner), nor is it nicely integrated into to sage (you
> have to `from pycrypto import foo`), to me it clearly falls into this boat.

Sage has a fairly clear mission statement: "Mission: Creating a viable
free open source alternative to Magma, Maple, Mathematica and Matlab."

Magma doesn't have crypto included, so far as I can tell:

   http://magma.maths.usyd.edu.au/magma/handbook/linear_codes_over_finite_fields

Do any other MA's?

William


>
> --
> Andrew
>
> --
> 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.



-- 
William Stein
Professor of Mathematics
University of Washington
http://wstein.org

-- 
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: Re: [sage-devel] The Annual Sage on Python 3 Thread

[William Stein]

On Wed, Dec 25, 2013 at 10:58 AM, Martin Albrecht
 wrote:
> On Wednesday 25 Dec 2013 09:09:58 Jean-Pierre Flori wrote:
>> I think having pycrypto in Sage is cool for ... cryptographers :)
>
> I am not sure this is true. PyCrypto is quite high-level, it gives you RSA,
> AES, SHA256 and sutff like that. At such a high level I guess it would be
> useful for testing/implementing protocols, but for the kind of crypto where
> Sage is probably used most - i.e. actually diving into the algorithms - I
> don't think it's that useful.

Even if you implement one of these, you might want to be able to very
easily compare your implementation against one that actually works.

> Put another way: did anybody on this list ever use it? I think I may have once
> briefly.

I have used it dozens of times in a teaching context (for undergrads).

 -- William

>
> Cheers,
> Martin
>
>
> --
> name: Martin Albrecht
> _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6532AFB4
> _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF
> _www: http://martinralbrecht.wordpress.com/
> _jab: martinralbre...@jabber.ccc.de



-- 
William Stein
Professor of Mathematics
University of Washington
http://wstein.org

-- 
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: Re: [sage-devel] The Annual Sage on Python 3 Thread

[R. Andrew Ohana]

I disagree with the sentiment that we should make python package X a
standard package because it is useful for Y. At that rate, every
(compatibly licensed) mathematics and science python package will be a
standard part of sage. Because pycrypto is not truly a dependency of the
sage library (i.e. used in a non-trivial manner), nor is it nicely
integrated into to sage (you have to `from pycrypto import foo`), to me it
clearly falls into this boat.

-- 
Andrew

-- 
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: Re: [sage-devel] The Annual Sage on Python 3 Thread

[Jean-Pierre Flori]

On a slightly unrelated topic, currently the only function of pycrypto used 
in the Sage library is indeed in the monoid stuff and that's the 
byte_to_long function.
Although I don't feel we should remove pycrypto from standard packages, I 
feel we could implement this ourselves if this prevents a boring warning 
from breaking tests (see #14854).

-- 
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: Re: [sage-devel] The Annual Sage on Python 3 Thread

[Jean-Pierre Flori]

On Wednesday, December 25, 2013 7:58:27 PM UTC+1, Martin Albrecht wrote:
>
> On Wednesday 25 Dec 2013 09:09:58 Jean-Pierre Flori wrote: 
> > I think having pycrypto in Sage is cool for ... cryptographers :) 
>
> I am not sure this is true. PyCrypto is quite high-level, it gives you 
> RSA, 
> AES, SHA256 and sutff like that. At such a high level I guess it would be 
> useful for testing/implementing protocols, but for the kind of crypto 
> where 
> Sage is probably used most - i.e. actually diving into the algorithms - I 
> don't think it's that useful. 
>
> Put another way: did anybody on this list ever use it? I think I may have 
> once 
> briefly. 

I think it can also be quite useful for teaching as well when you want to 
jump from more crypto oriented to more math oriented stuff. 

-- 
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: Re: [sage-devel] The Annual Sage on Python 3 Thread

[Martin Albrecht]

On Wednesday 25 Dec 2013 09:09:58 Jean-Pierre Flori wrote:
> I think having pycrypto in Sage is cool for ... cryptographers :)

I am not sure this is true. PyCrypto is quite high-level, it gives you RSA, 
AES, SHA256 and sutff like that. At such a high level I guess it would be 
useful for testing/implementing protocols, but for the kind of crypto where 
Sage is probably used most - i.e. actually diving into the algorithms - I 
don't think it's that useful.

Put another way: did anybody on this list ever use it? I think I may have once 
briefly.

Cheers,
Martin


--
name: Martin Albrecht
_pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6532AFB4
_otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF
_www: http://martinralbrecht.wordpress.com/
_jab: martinralbre...@jabber.ccc.de

signature.asc
Description: This is a digitally signed message part.

Re: [sage-devel] Reviewing package version updates (in particular, gap)

[Jean-Pierre Flori]

On Wednesday, December 25, 2013 7:45:05 PM UTC+1, François wrote:
>
> Going back to the general subject. Could we have a shortcut on the ticket 
> report page 
> grabbing update/upgrade of packages. Unless the potential reviewer(s) are 
> cc automatically 
> that would any review easier, as in more easy to find. 
>
> Grep update or upgrade in the ticket title? 

-- 
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] Reviewing package version updates (in particular, gap)

[Francois Bissey]

Going back to the general subject. Could we have a shortcut on the ticket 
report page
grabbing update/upgrade of packages. Unless the potential reviewer(s) are cc 
automatically
that would any review easier, as in more easy to find.

François

From: sage-devel@googlegroups.com [sage-devel@googlegroups.com] on behalf of 
Francois Bissey [francois.bis...@canterbury.ac.nz]
Sent: Wednesday, 25 December 2013 12:15
To: sage-devel@googlegroups.com
Subject: RE: [sage-devel] Reviewing package version updates (in particular, gap)

No. And yes that means I volunteer. Of course that means that sometimes I'll
just be a second pair of eyes to spot any glaring stuff we don't want.
The buildbot reviews a number of things far better than a single reviewer can 
do.

François

From: sage-devel@googlegroups.com [sage-devel@googlegroups.com] on behalf of 
Volker Braun [vbraun.n...@gmail.com]
Sent: Wednesday, 25 December 2013 12:01
To: sage-devel@googlegroups.com
Subject: [sage-devel] Reviewing package version updates (in particular, gap)

The current process of updating third-party packages is broken:

a) There isn't really anything to review beyond running it on the buildbot
b) Nobody dares to press the "positive review" button
c) Frustation to see your work waste away on trac

for example, out of the last three Gap package updates that I packaged only one 
was ever looked at. So I'm proposing that I'll just merge package updates if 
they *work* as long as there isn't too much wonkyness introduced into the build 
script. If you have any opinion on that, please post in this thread :-)

[ ]  Yes, go ahead
[ ]  No, I want to volunteer as the reviewer for package upgrades

See also: http://trac.sagemath.org/15582

--
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.

This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.

Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.

--
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.

This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.

Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.

-- 
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: Reviewing package version updates (in particular, gap)

[Jean-Pierre Flori]

On Wednesday, December 25, 2013 7:08:15 PM UTC+1, Volker Braun wrote:
>
> On Wednesday, December 25, 2013 5:52:39 PM UTC, Jean-Pierre Flori wrote:
>>
>> #12399
>>
>
> I just want to point out that this took you half a year... IMHO there is 
> no point to if if it takes longer than the upstream release cycle ;-)
>  
>
Note that this patch is not upstream yet, and apart from Stephen (who 
maintains its own FreeBSD port with needed patches) and sometimes me, I'm 
not sure that anyone builds Sage on FreeBSD.
So I was not very reactive to finalize it (in fact it was not working 
before today, my bad) and make it get in.
I just happened to have some time this afternoon and took care of it, 
surely because of your post.

-- 
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: Reviewing package version updates (in particular, gap)

[Volker Braun]

On Wednesday, December 25, 2013 5:52:39 PM UTC, Jean-Pierre Flori wrote:
>
> #12399
>

I just want to point out that this took you half a year... IMHO there is no 
point to if if it takes longer than the upstream release cycle ;-)
 

-- 
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: Reviewing package version updates (in particular, gap)

[Jean-Pierre Flori]

I'd prefer to have a quick review for everything.
Just having someone else having a quick look at the diff is also a good 
idea, and I think the peer-reviewing system of Sage is a real plus value.

By the way a bunch of more or less trivial updates, upstream patch 
inclusion: #12399, #14333, #14854, #15365, #15366, #15574, #15586, #15589 :)
(Ok, some of these need porting to the new layout.)

-- 
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: sage -upgrade idiosyncracies

[P Purkayastha]

Yes.

The output of make (run again; nothing to update) is attached. There are 
no differences between github, trac and my local develop branch.


~/Installations/sage» git rev-parse --abbrev-ref HEAD
develop
~/Installations/sage» git diff develop origin/develop
~/Installations/sage» diff -q local/bin/sage-upgrade src/bin/sage-upgrade
Files local/bin/sage-upgrade and src/bin/sage-upgrade differ
~/Installations/sage [1] »  git diff develop trac/develop
~/Installations/sage»

On 12/26/2013 12:32 AM, Volker Braun wrote:

You need to run "make" to install the updated scripts in local/, did you
do that?

On Wednesday, December 25, 2013 4:21:51 PM UTC, P Purkayastha wrote:

Well, that's the problem. local/bin is not tracked by git. And I am not
sure how else I can force the upgrade of the scripts. In terms of the
sage library, I am already on sage-6.1.beta2.

On 12/26/2013 12:12 AM, Volker Braun wrote:
 > It seems your first installation is pre-6.0. Before that was
released
 > there were bugs in the upgrade script. Use git to manually
upgrade to
 > 6.0 first, then "sage -upgrade" will (should) work.
 >
 >
 > On Wednesday, December 25, 2013 2:22:43 PM UTC, P Purkayastha wrote:
 >
 > With the second method it is all very smooth. I did a
 > .../src/sage/sage-6.0.server> git fetch origin
 >
 >
 > The fetch is also performed by the upgrade script, no need to do it
 > manually.
 >
 > followed by
 > .../src/sage/sage-6.0.server> ./sage -upgrade develop
 >
 >
 > --
 > You received this message because you are subscribed to the Google
 > Groups "sage-git" group.
 > To unsubscribe from this group and stop receiving emails from it,
send
 > an email to sage-git+u...@googlegroups.com .
 > For more options, visit https://groups.google.com/groups/opt_out
.

--
You received this message because you are subscribed to the Google
Groups "sage-git" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to sage-git+unsubscr...@googlegroups.com.
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.
~/Installations/sage» make
cd build && \
"../build/pipestatus" \
"env SAGE_PARALLEL_SPKG_BUILD='' ./install all 2>&1" \
"tee -a ../logs/install.log"
Nothing to (re)build / all up-to-date.
./sage -b
scons: `install' is up to date.
Updating Cython code
Finished compiling Cython code (time = 2.21100997925 seconds)
running install
running build
running build_py
running build_ext
warning: Replacing library search directory in linker command:
  "/tmp/sage/local/lib" -> "/mnt/usb/Installations/sage/local/lib"

Executing 0 commands (using 1 thread)
Time to execute 0 commands: 0.00230002403259 seconds
Total time spent compiling C/C++ extensions:  0.0993618965149 seconds.
running install_lib
running install_egg_info
Removing 
/mnt/usb/Installations/sage/local/lib/python2.7/site-packages/sage-6.1.beta2-py2.7.egg-info
Writing 
/mnt/usb/Installations/sage/local/lib/python2.7/site-packages/sage-6.1.beta2-py2.7.egg-info

real0m3.227s
user0m2.853s
sys 0m0.267s
[ -f local/etc/sage-started.txt ] || local/bin/sage-starts
build/pipestatus "./sage --docbuild --no-pdf-links all html  2>&1" "tee -a 
logs/dochtml.log"

Building reference manual, first pass.

[combinat ] no targets are out of date.
[polynomia] no targets are out of date.
[cmd  ] no targets are out of date.
[dynamics ] no targets are out of date.
[arithgrou] no targets are out of date.
[graphs   ] no targets are out of date.
[homology ] no targets are out of date.
[misc ] no targets are out of date.
[notebook ] no targets are out of date.
[algebras ] no targets are out of date.
[calculus ] no targets are out of date.
[categorie] no targets are out of date.
[coding   ] no targets are out of date.
[coercion ] no targets are out of date.
[constants] no targets are out of date.
[cryptogra] no targets are out of date.
[databases] no targets are out of date.
[dev  ] no targets are out of date.
[diophanti] Configuration error:
[diophanti] There is a syntax error in your configuration file: invalid syntax 
(conf.py, line 1)
[doctest  ] no targets are out of date.
[finance  ] no targets are out of date.
[finite_ri] no targets are out of date.
[function_] no targets are out of date.
[functions] no targets are out of date.
[games] no targets are out of date.
[geometry ] no targets are out of date.
[groups   ] no targets are

Re: [sage-devel] The Annual Sage on Python 3 Thread

[Jean-Pierre Flori]

On Wednesday, December 18, 2013 6:24:40 AM UTC+1, R. Andrew Ohana wrote:
>
> I've made #15530 to track the progress on supporting python3 (and there is 
> already a good amount there that is up for review).
>
>
> Also, other than the trivial usage in 
> sage.monoids.string_monoid(_element), I'm not finding any real usage of 
> pycrypto. Am I missing something? If not, I would elect to make it an 
> optional package.
>
I think having pycrypto in Sage is cool for ... cryptographers :)
Hint: fix for FreeBSD at #12399 and update to latest upstream at #14854! 

-- 
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: sage -upgrade idiosyncracies

[Volker Braun]

You need to run "make" to install the updated scripts in local/, did you do 
that?

On Wednesday, December 25, 2013 4:21:51 PM UTC, P Purkayastha wrote:
>
> Well, that's the problem. local/bin is not tracked by git. And I am not 
> sure how else I can force the upgrade of the scripts. In terms of the 
> sage library, I am already on sage-6.1.beta2. 
>
> On 12/26/2013 12:12 AM, Volker Braun wrote: 
> > It seems your first installation is pre-6.0. Before that was released 
> > there were bugs in the upgrade script. Use git to manually upgrade to 
> > 6.0 first, then "sage -upgrade" will (should) work. 
> > 
> > 
> > On Wednesday, December 25, 2013 2:22:43 PM UTC, P Purkayastha wrote: 
> > 
> > With the second method it is all very smooth. I did a 
> > .../src/sage/sage-6.0.server> git fetch origin 
> > 
> > 
> > The fetch is also performed by the upgrade script, no need to do it 
> > manually. 
> > 
> > followed by 
> > .../src/sage/sage-6.0.server> ./sage -upgrade develop 
> > 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> > Groups "sage-git" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> > an email to sage-git+u...@googlegroups.com . 
> > 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.

[sage-devel] Re: sage -upgrade idiosyncracies

[P Purkayastha]

Well, that's the problem. local/bin is not tracked by git. And I am not 
sure how else I can force the upgrade of the scripts. In terms of the 
sage library, I am already on sage-6.1.beta2.


On 12/26/2013 12:12 AM, Volker Braun wrote:

It seems your first installation is pre-6.0. Before that was released
there were bugs in the upgrade script. Use git to manually upgrade to
6.0 first, then "sage -upgrade" will (should) work.


On Wednesday, December 25, 2013 2:22:43 PM UTC, P Purkayastha wrote:

With the second method it is all very smooth. I did a
.../src/sage/sage-6.0.server> git fetch origin


The fetch is also performed by the upgrade script, no need to do it
manually.

followed by
.../src/sage/sage-6.0.server> ./sage -upgrade develop


--
You received this message because you are subscribed to the Google
Groups "sage-git" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to sage-git+unsubscr...@googlegroups.com.
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.

[sage-devel] Re: sage -upgrade idiosyncracies

[Volker Braun]

It seems your first installation is pre-6.0. Before that was released there 
were bugs in the upgrade script. Use git to manually upgrade to 6.0 first, 
then "sage -upgrade" will (should) work.


On Wednesday, December 25, 2013 2:22:43 PM UTC, P Purkayastha wrote:
>
> With the second method it is all very smooth. I did a
> .../src/sage/sage-6.0.server> git fetch origin 
>

The fetch is also performed by the upgrade script, no need to do it 
manually.
 

> followed by 
> .../src/sage/sage-6.0.server> ./sage -upgrade develop 
>

 

-- 
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: #15441 needs_review Clean up ecl SIGCHLD configuration

[Jean-Pierre Flori]

Done.

On Wednesday, December 25, 2013 2:03:29 PM UTC+1, Volker Braun wrote:
>
> This should be an easy one... I think everything that can be said on the 
> ticket has already been, it just then fizzled out without somebody pressing 
> positive review...
>
> http://trac.sagemath.org/ticket/15441
>

-- 
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: Reviewing package version updates (in particular, gap)

[Volker Braun]

Done

On Wednesday, December 25, 2013 1:36:02 AM UTC, Volker Braun wrote:
>
> I forgot to push my branch
>

-- 
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] 404 on Sage Developer Conventions

[Darij Grinberg]

Hi guys,

this site is now 404:
http://www.sagemath.org/doc/developer/conventions.html
Where has it moved?

  Best regards,
  Darij

-- 
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] sage -upgrade idiosyncracies

[P Purkayastha]

I had set up sage-git in two ways. The first one was by following the 
quickstartguide [1]. The second way was by using the sage-6.0 tarball.


First method (Quickstartguide):
---

Now, with the first method, it seems impossible to run sage -upgrade and 
have it behave properly. Here is an example output:


~/Installations/sage» ./sage -upgrade develop
fatal: 'develop' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
There was a failure downloading Sage's sources. Please make sure you are 
connected to the internet. Aborting...

~/Installations/sage [1] »


This error is present even though the develop branch is present in the 
remote repository:


~/Installations/sage [1] » git branch -r | grep origin
  origin/HEAD -> origin/master
  origin/develop
  origin/master
  origin/upstream

The following command partially works:

~/Installations/sage» ./sage -upgrade g...@trac.sagemath.org:sage.git develop
From trac.sagemath.org:sage
 * [new branch]  develop-> zKYBy6_CBUB4D3fkr1eEgEY5-lmwod6sahiGr0V8
Already up-to-date.
Deleted branch zKYBy6_CBUB4D3fkr1eEgEY5-lmwod6sahiGr0V8 (was 036984d).
/mnt/usb/Installations/sage/local/bin/sage-upgrade: line 59: 
sage-real-upgrade: command not found


Followed this by a "make" and it recompiled maxima, and other than that 
I do not see any other changes.


Second method (sage-6.0 tarball):
-

With the second method it is all very smooth. I did a

.../src/sage/sage-6.0.server> git fetch origin

followed by

.../src/sage/sage-6.0.server> ./sage -upgrade develop



The main problem:
-

After a bit more investigating, it turns out that most of the scripts in 
SAGE_ROOT/local/bin are all at some old version from Dec 14. A bunch of 
questions:


1. So, even though I started out with sage-git from pre-6.0 version, at 
some point sage itself got upgraded but not installed (at least the 
scripts)?


2. How can I (manually) install the new scripts? Should I just copy the 
files from src/bin?


3. How can I prevent this problem from recurring in the future?


[1] http://trac.sagemath.org/wiki/QuickStartSageGit

--
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] #15441 needs_review Clean up ecl SIGCHLD configuration

[Volker Braun]

This should be an easy one... I think everything that can be said on the 
ticket has already been, it just then fizzled out without somebody pressing 
positive review...

http://trac.sagemath.org/ticket/15441

-- 
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] Polynomials over non-commutative rings

[Charles Bouillaguet]

On 23 Dec 2013, at 10:27, Marc Mezzarobba  wrote:

> Vincent Delecroix wrote:
>> Does polynomial over non-commutative ring make sense ? Because in that
>> context axbx is not abx^2. Depending on what you call polynomial, they
>> may or may not form a ring.

The polynomials over matrices with scalar coefficients are probably an instance 
of what Marc means...

---
Charles Bouillaguet
http://www.lifl.fr/~bouillaguet/



-- 
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.