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

2016-01-14 Thread Emmanuel Charpentier
FWIW, passes ptestlong with no errors on Debian testing running on Core i7 
w/ 16 Gb RAM.

HTH,

--
Emmanuel Charpentier

Le jeudi 14 janvier 2016 02:08:45 UTC+1, Volker Braun a écrit :
>
> 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.


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

2016-01-14 Thread kcrisman


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


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

2016-01-14 Thread Jeroen Demeyer

On 2016-01-14 15:48, kcrisman wrote:

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

--
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-14 Thread kcrisman

>
>
> 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.
>
>
>
I looked through several of the threads in sage-release but couldn't 
(quickly) find anything more detailed than this.  What happened that Sage 7 
is not upgradeable?

I think that it would then make sense to have some message print out if 
someone tries sage -upgrade (if that's even still supported) lest they hose 
their Sage install, that's been a problem with such updates in the past as 
well. 

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?

Thanks,
- kcrisman

-- 
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: error: Cannot perform incremental update

2016-01-14 Thread Nathann Cohen
> I guess you mean "make distclean && make" (double ampersand)

I did.

Nathann

-- 
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: error: Cannot perform incremental update

2016-01-14 Thread Jeroen Demeyer

On 2016-01-14 09:15, Volker Braun wrote:

After you run "make distclean & make", is lib64 a symlink? If its not
then its a bug.


I guess you mean "make distclean && make" (double ampersand)

--
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: error: Cannot perform incremental update

2016-01-14 Thread Nathann Cohen
> If "make distclean" fails then its not going to do anything, duh. Delete
> SAGE_LOCAL by hand or "git clean -f -d -x"

'make distclean' did not fail: only 'make' failed. And I am not stuck:
the first call to 'make' fails with the error reported above, but the
second worked alright and I am now reviewing #19586 :-)

Nathann

-- 
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: error: Cannot perform incremental update

2016-01-14 Thread Volker Braun
If "make distclean" fails then its not going to do anything, duh. Delete 
SAGE_LOCAL by hand or "git clean -f -d -x"




On Thursday, January 14, 2016 at 9:22:54 AM UTC+1, Nathann Cohen wrote:
>
> > After you run "make distclean & make", is lib64 a symlink? If its not 
> then 
> > its a bug. 
>
> After this double "make" (the first that fails with the message above, 
> the second that works) it is a regular directory. If it happens again 
> I will post here. 
>
> Nathann 
>

-- 
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: error: Cannot perform incremental update

2016-01-14 Thread Nathann Cohen
> After you run "make distclean & make", is lib64 a symlink? If its not then
> its a bug.

After this double "make" (the first that fails with the message above,
the second that works) it is a regular directory. If it happens again
I will post here.

Nathann

-- 
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: error: Cannot perform incremental update

2016-01-14 Thread Volker Braun
After you run "make distclean & make", is lib64 a symlink? If its not then 
its a bug.



On Thursday, January 14, 2016 at 7:32:55 AM UTC+1, Nathann Cohen wrote:
>
> Hello everybody, 
>
> For the latest beta releases, each time 'git pull && make' produced 
> the following message: 
>
> ... 
> config.status: /home/ncohen/.Sage/local/lib64 is not a symlink, 
> see Trac #19782 
> config.status: error: Cannot perform incremental update, run "make 
> distclean && make" 
>
> I think I once followed the advice and ran a 'make distclean & make', 
> though I also noticed that running 'make' right after this error lead 
> to a successful compilation. 
>
> My install is not broken in any way that I can tell, but it looked 
> weird to see this 'cannot perform incremental update' message 
> repeatedly (I thought it would only happen 'one time', then work for 
> all subsequent updates) and so I report it. 
>
> Nathann 
>

-- 
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] error: Cannot perform incremental update

2016-01-14 Thread Henri Girard
I used to have this problem too... So I didn't know how to correct it 
now I create a new git to each version and I have no more problem... 
(but that's not a way to improve correcting problems ! )

Henri

Le 14/01/2016 08:41, Nathann Cohen a écrit :

Yo,


This should if and only if you upgrade from Sage <= 7.0.beta1 to Sage >=
7.0.beta2.

It definitely happened several times.


Maybe you just switched between old and new branches?

No, the way I work with git this is not possible.

Nathann



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