Re: [sage-release] Re: Sage 8.3.beta1 released

Bionic 18.04 AMD x8 64 bits, compile perfect. I started from fresh git sage because upgrading from 8.2 failed. It couldn't find many libs. By the way I found my crash problem while compiling : I had to config the bios allowing warmer processing. Le 15/05/2018 à 21:24, Sébastien Labbé a écrit 

Re: [sage-release] Re: Release process

On 15/05/2018 17:07, Volker Braun wrote: The integration branch is going to have its history rewritten regularly. Why is that? Shouldn't the process be simply 1. create a branch TMP = "integration branch" + "merged positive review ticket" 2. if merge fails: move back ticket to needs work

Re: [sage-release] Re: Release process

On 2018-05-16 11:26, Vincent Delecroix wrote: It can be smarter than a hash, e.g. 8.3.beta2018-05-16. And we can afford a daily release at GMT 00:00. If you want to automate it anyway, you could instead automatically release a new "beta" whenever develop is updated. -- You received this

Re: [sage-release] Re: Sage 8.3.beta1 released

I started to build this yesterday after pulling from trac into a place where beta0 had already built OK. This morning I find the lines [scipy-0.19.1] Skipping scipy as it is not installed. [scipy-0.19.1] Skipping scipy as it is not installed. [scipy-0.19.1] Skipping scipy as it is not installed.

Re: [sage-release] Re: Release process

On 2018-05-16 10:23, Vincent Delecroix wrote: TMP is public! People should just not base their work on as it is likely to be abandoned. On the other hand, people should be encouraged to base their work on "integration" and not on "latest beta". It seems that you're thinking that there are 3

Re: [sage-release] Sage 8.3.beta0 released

in this case doctest basically compares strings, obtained from the list of roots. Order of the latter is not important. By right, one should compare sets, not lists. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group

Re: [sage-release] Re: Release process

On 2018-05-16 10:30, Vincent Delecroix wrote: And I agree: there should be two branches whatever they are called. Let's go for "develop + integration" (that were "integration" + "TMP" in my previous e-mail). In that case, I fully agree with your previous e-mail! As a consequence, we would

Re: [sage-release] Re: Release process

On 2018-05-16 10:06, Vincent Delecroix wrote: On 15/05/2018 17:07, Volker Braun wrote: The integration branch is going to have its history rewritten regularly. Why is that? Shouldn't the process be simply 1. create a branch TMP = "integration branch" + "merged positive review ticket"

Re: [sage-release] Re: Release process

On 16/05/2018 10:57, Jeroen Demeyer wrote: On 2018-05-16 10:30, Vincent Delecroix wrote: And I agree: there should be two branches whatever they are called. Let's go for "develop + integration" (that were "integration" + "TMP" in my previous e-mail). In that case, I fully agree with your

Re: [sage-release] Re: Release process

On 16/05/2018 10:15, Jeroen Demeyer wrote: On 2018-05-16 10:06, Vincent Delecroix wrote: On 15/05/2018 17:07, Volker Braun wrote: The integration branch is going to have its history rewritten regularly. Why is that? Shouldn't the process be simply    1. create a branch TMP = "integration

Re: [sage-release] Re: Release process

On 16/05/2018 10:26, Jeroen Demeyer wrote: On 2018-05-16 10:23, Vincent Delecroix wrote: TMP is public! People should just not base their work on as it is likely to be abandoned. On the other hand, people should be encouraged to base their work on "integration" and not on "latest beta". It

Re: [sage-release] Re: Sage 8.3.beta1 released

On Wed, May 16, 2018 at 9:56 AM, John Cremona wrote: > I started to build this yesterday after pulling from trac into a place where > beta0 had already built OK. This morning I find the lines > > [scipy-0.19.1] Skipping scipy as it is not installed. > [scipy-0.19.1]

Re: [sage-release] Sage 8.3.beta0 released

On 16 May 2018 at 12:06, Samuel Lelièvre wrote: > Would changing the doctest from > > sage: pol.roots(multiplicities=False, proof=False) > > to > > sage: sorted(pol.roots(multiplicities=False, proof=False)) > > solve this? > I think that in other places where

Re: [sage-release] Re: Release process

On 2018-05-16 12:44, Vincent Delecroix wrote: - "integration" is intended to be used by bots only to check whether a given positively reviewed ticket is worth a merge. It has no reason to be used by any human. The issue is that it may be accidentally used by a human by mistake. -- You

Re: [sage-release] Sage 8.3.beta0 released

Would changing the doctest from sage: pol.roots(multiplicities=False, proof=False) to sage: sorted(pol.roots(multiplicities=False, proof=False)) solve this? 2018-05-16 10:16 GMT+02:00 Dima Pasechnik : > in this case doctest basically compares strings, > obtained

Re: [sage-release] Re: Sage 8.3.beta1 released

pip should be able to uninstall itself so sage -pip uninstall pip sage -i pip should give you the standard sage version of pip back. I did not test this, so use at your own risk. On Wednesday, 16 May 2018 17:33:50 UTC+2, John Cremona wrote: > > > > On Wed, 16 May 2018, 16:26 Erik Bray,

Re: [sage-release] Re: Release process

* Some buildbots are too slow to run the entire testsutie for every ticket * Sometimes tests fail because of unrelated tickets are randomly failing * Sometimes tests succeed even if the ticket introduces a random failure * Sometimes buildbots are offline for a day, need rebooting, etc. *

Re: [sage-release] Re: Sage 8.3.beta1 released

On 2018-05-16 17:26, Erik Bray wrote: I'm not sure, but I think this might be pip-related. I think Jeroen mentioned something about this to me a couple weeks ago. Is it possible you upgraded the pip in your Sage install? Indeed, I guess you are using pip 10 by accident. It might be a good