Re: [sage-release] Re: Sage 7.0.rc1 released

2016-01-15 Thread Henri Girard

Thanks... Because each time I get a new develop version.
Try it next version.
Henri

Le 15/01/2016 11:40, Johan S. R. Nielsen a écrit :

If you already have a nice compiled version of latest develop, you can
merge in your old branch *into* develop. With latest develop checked
out, run the following:

1. git checkout -b "old_is_new"
2. git fetch 
3. git merge trac/
4. make

Step 2 is only if you don't already have the latest version of that ticket.

Compared to the newly compiled develop, this will touch only the files
that were modified in your ticket. That saves a lot of compilation time
when you're working on branches that have fallen far behind. That goes
whether or not latest develop broke backwards compatibility.

Best,
Johan


kcrisman writes:


Also, can you give a little more guidance on how to still use "old" git

branches - can we just merge in the newest Sage or will that cause
problems as well?

If moving from a new branch to an old branch, you can either
- merge in latest develop, or
- make distclean && make



Second option isn't very sustainable if you have to do it a lot, though.


--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


[sage-release] Re: Sage 7.0.rc1 released

2016-01-15 Thread Eric Gourgoulhon
built OK + make ptestlong passed on Ubuntu 15.10 x86_64 Xeon E5-2623 + 16 
GB RAM. 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-release] Re: Sage 7.0.rc1 released

2016-01-15 Thread Johan S . R . Nielsen
If you already have a nice compiled version of latest develop, you can
merge in your old branch *into* develop. With latest develop checked
out, run the following:

1. git checkout -b "old_is_new"
2. git fetch 
3. git merge trac/
4. make

Step 2 is only if you don't already have the latest version of that ticket.

Compared to the newly compiled develop, this will touch only the files
that were modified in your ticket. That saves a lot of compilation time
when you're working on branches that have fallen far behind. That goes
whether or not latest develop broke backwards compatibility.

Best,
Johan


kcrisman writes:

>> Also, can you give a little more guidance on how to still use "old" git 
>> > branches - can we just merge in the newest Sage or will that cause 
>> > problems as well? 
>>
>> If moving from a new branch to an old branch, you can either 
>> - merge in latest develop, or 
>> - make distclean && make 
>>
>>
> Second option isn't very sustainable if you have to do it a lot, though. 

-- 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


[sage-release] Sage 7.0.rc1 released

2016-01-15 Thread Johan S . R . Nielsen
Built and passed ptestlong on Arch Linux 64bit, fully up-to-date, 16GB ram.

Best,
Johan


Volker Braun writes:

> As always, you can get the latest beta version from the "develop" git 
> branch. Alternatively, the self-contained source tarball is at 
> http://www.sagemath.org/download-latest.html
>
> As mentioned before, there are no incremental updates from 6.x. You need to 
> compile from scratch, e.g. after cleaning with "make distclean" or "git 
> clean -f -d -x". If you are still working on tickets based on 6.x then you 
> might want to use a separate git tree for sage 7.
>
> adef4de Updated Sage version to 7.0.rc1
> f6287c1 Trac #19880: update openssl to 1.0.2e
> ae128a3 Trac #17785: crash in multipolynomial substitutions
> b39fa51 Trac #19781: Move broken optional packages to experimental
> e5af38d Trac #15348: "R. =" syntactic sugar incorrect for EquationOrder
> d652c8b Trac #19750: singular genus crash
> f35ec3b Updated Sage version to 7.0.rc0

-- 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.